- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 Mar 2021 18:16:44 +0000
- To: public-css-archive@w3.org
Specs can't force implementations; they exist to help increase interoperability *between* implementations (and guide the design of features in conjunction with the impls). We currently have one major impl (Safari) with a stated preference for *definitely not* doing this, and the other impls are at best apathetic about the feature at the moment. So, from the spec side of things, there's not much we can do; I prefer writing specifications, not speci-fiction. ^_^ From the author side, you can put pressure on the impls by filing bugs or +1ing existing bugs, and/or making noise and gathering support on blogs and social media. If the impls change their stance as a result of webdev pressure, we can revisit the issue. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6090#issuecomment-801304614 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 17 March 2021 18:16:46 UTC