Re: [csswg-drafts] Let’s Define CSS 4 (#4770)

While agreeing that promoting the current evolment of CSS as a version 4 might re-create the former buzz of “CSS3”, let’s not ignore the fact that also many professionals weren’t able to use these then new features due to project constraints such as browser support and stubborn project- or tech-leads. I used to work for a company back then that forbid the usage of vendor-prefixes and every single CSS3 feature due to a “lowest common denominator approach” of ensureing browser support, as it was seen as a way to avoid “extra work”. The last agency I worked for, to this day, is trying to avoid flexbox since it is “hard to understand” and “is behaving unpredictably”. Although we have new and more efficient ways to progressively enhance our websites etc. I can imagine that this would still be a reality for a lot of developers out there. Also, perhaps you have noticed the usage of the word “might”. The status of JS back then was also a bit different. So I have serious doubts if CSS4 would actually create the same marketing effect today that CSS3 was able to generate. 

Also I am afraid that browser vendors might slow down when it comes to implement these new features since it then would make sense to wait until a new version is “complete” of “worth” supporting. 
Grid IMO was so successful because it solved a decade old problem CSS devs were facing but also due to the fast pace in which the browser vendors were picking it up (and great learning material by Jen & Rachel etc.). 

I’d personally like to see a just as lively discussion about how we could push CSS & progressive enhancement more as a whole than CSS4 etc. since it feels like the more concrete lever to pull here. 

-- 
GitHub Notification of comment by marekgebka
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4770#issuecomment-587168948 using your GitHub account

Received on Monday, 17 February 2020 21:46:34 UTC