- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 21 Apr 2021 17:57:14 +0000
- To: public-css-archive@w3.org
> My understanding given the supports syntax in drafts.csswg.org/css-conditional/#typedef-supports-condition is that this is a Chromium / WebKit bug. Does it match yours @lilles? Firefox's behavior is intended to be correct, but I note that @supports does not define what to do with an unknown value that's escaped to the top level (@media does: <https://drafts.csswg.org/mediaqueries-5/#evaluating>). That needs fixing. > And these need specific definitions because <media-query> has a <general-enclosed> clause that would parse all media queries successfully (I think this is a mediaqueries-4 feature which we weren't implementing). If you don't implement that, fwiw, then it's not safe for authors to use the new at-rule() or container() or whatever functions, since they'll invalidate the entire rule in older versions. :/ -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6175#issuecomment-824249502 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 21 April 2021 17:57:17 UTC