- From: Daniel McFarland via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Feb 2020 18:31:20 +0000
- To: public-css-archive@w3.org
@rickgregory So how do you coordinate a marketing effort like this that depends so much on what browser vendors choose to do (or not do)? For this to be successful, I think it needs to focus more on defining what sets of CSS features are actually supported in some subset of (currently available) browsers/versions and less on trying to coordinate with browser vendors to all support a set of CSS features on a timeline that allows it to be "marketed" ahead of release. I would hope that this process would eventually encourage vendors to coordinate with whoever is defining these CSS "versions," but it seems pretty ambitious to think that it would happen right away. And no matter how a CSS "version" is defined, it will still be up to the front line dev to make a judgement call on what version to use/support based on their particular audience. -- GitHub Notification of comment by 29thfloor Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4770#issuecomment-591574100 using your GitHub account
Received on Wednesday, 26 February 2020 18:31:22 UTC