- From: Rune Lillesveen via GitHub <sysbot+gh@w3.org>
- Date: Wed, 21 Apr 2021 18:03:26 +0000
- To: public-css-archive@w3.org
> ```js
> CSS.supports("not foo()")
> ```
>
> That returns `true` in Firefox (as I'd expect, fwiw), but `false` in Chrome and Safari. So you can't use `@supports not container(..)` unless they implement the new thing. We should probably get interop on that. My understanding given the supports syntax in https://drafts.csswg.org/css-conditional/#typedef-supports-condition is that this is a Chromium / WebKit bug. Does it match yours @lilles?
I think that `foo()` is `<general-enclosed>` which is unknown, and `not unknown` is unknown, and I couldn't figure out how uknown should be handled.
--
GitHub Notification of comment by lilles
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6175#issuecomment-824253261 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 18:03:42 UTC