- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Dec 2016 02:45:02 +0000
- To: public-css-archive@w3.org
I think this is a case where we know what the right thing to do is, we know how to spec it, and the only problem is implements not prioritizing it due to it being a corner case. For such things, I'd suggest marking the feature at risk, with a note that if we fail to get 2 implementations, we'll drop the requirement from must to should for this level (with the intent to bring it back as a must in a later level). Adding a note for authors telling them how to work around it if a browser does not follow the recommendation sounds useful as well, but I'd want that in addition to the normative prose, not instead of it, as we still want to push implement to do the right thing eventually. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/755#issuecomment-265045150 using your GitHub account
Received on Tuesday, 6 December 2016 02:45:17 UTC