- From: rickgregory via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Feb 2020 16:52:16 +0000
- To: public-css-archive@w3.org
@29thfloor - it's not just less technical people who are helped by labels like CSS4 etc but front line devs too. It defines a package of CSS features that are all ready for prime-time... which brings me to a point that seems under-discussed... implementing by browser vendors. One reason CSS3 and HTML5 worked well is that they were fully or mostly fully implemented in browsers. I'm probably eliding some issues because it's been awhile but if a feature set is not only part of a CSSX release but that release is also coordinated with browser releases then we know we can use them in production. Sure, we can always use advanced features with partial implementation as enhancements, but the reality of client schedules is that often you just don't do the enhancement at all because it's extra work and testing that only benefits some smaller percentage of visitors. That's one reason Grid was so successful at rollout - we knew that browsers as of a certain date all implemented I, we could see when those browsers became the vast majority of the traffic for a client and then we could deploy. -- GitHub Notification of comment by rickgregory Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4770#issuecomment-591528798 using your GitHub account
Received on Wednesday, 26 February 2020 16:52:18 UTC