- From: Bramus! via GitHub <sysbot+gh@w3.org>
- Date: Mon, 13 Feb 2023 12:18:30 +0000
- To: public-css-archive@w3.org
> So `@supports selector (&) {}` is no longer usable as a **reliable** detection?
_(Cross-posting from Chromium’s I2S)_
Authors can work around Chrome 109+110 incorrectly reporting `&` support by also testing for a feature that ships in any release after Chrome 110. A good candidate would be `cos()`, which ships in Chrome 111:
```css
@supports selector(&) and (scale: cos(90deg)) {
…
}
```
This check excludes Chrome 109+110, but includes Chrome 111 with the feature flag on.
More importantly this extended check won’t exclude Safari or Firefox, as they too support `cos()` – from, respectively, versions 15.4 and 108 onwards [according to caniuse.com](https://caniuse.com/mdn-css_types_cos).
--
GitHub Notification of comment by bramus
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8399#issuecomment-1427847117 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 13 February 2023 12:18:32 UTC