- From: Jeremy Fuksa via GitHub <sysbot+gh@w3.org>
- Date: Thu, 13 Feb 2020 17:11:58 +0000
- To: public-css-archive@w3.org
Lots of great points here. As many pointed out, it seems like moving to a naming convention similar to what ECMAScript adopted makes a lot of sense. And, there could be ways to delineate experimental features and account for @rachelandrew‘s concerns. Whatever is “ready” (e.g. @zeldman‘s suggestion of at least two major engine implementations) is in the CSS4/2020 spec. Everything else is experimental and could be adopted by browsers and implemented through config flags or browser prefixing. As for how often this spec gets updated, I’m in @folletto’s camp that yearly might be too much. That’s just going to fuel the fire that we’re never going to catch up with the building blocks that are the foundation of our livelihoods. 3 years seems like a nice number because that will also allow for accumulation of features that make a new spec worth learning while (hopefully) minimizing that FUD of never catching up. -- GitHub Notification of comment by jeremyfuksa Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4770#issuecomment-585867025 using your GitHub account
Received on Thursday, 13 February 2020 17:12:10 UTC