- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 29 Jan 2019 22:32:21 +0000
- To: public-css-archive@w3.org
There's no good solution to this that doesn't break the fundamental value proposition of `@supports`, which is that, since it's based purely on "does it parse", it requires *no* special table of return results in the browser, which history has shown us is destined to become some combination of stale and lies. I'm strongly against anything that tries to get "special-case" answers like this that aren't backed by a simple "try to parse it" mechanism. (I definitely feel the pain, but it's not solveable here without making things overall worse.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3559#issuecomment-458734231 using your GitHub account
Received on Tuesday, 29 January 2019 22:32:23 UTC