- From: Sebastian Zartner via GitHub <noreply@w3.org>
- Date: Tue, 02 Sep 2025 11:13:14 +0000
- To: public-css-archive@w3.org
SebastianZ has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-2025][selectors-4] Add Selectors 4 to Rough Interop == Splitting the discussion from #9793 for adding [Selectors 4](https://www.w3.org/TR/selectors-4/) to the Modules with Rough Interoperability section of the CSS Snapshot 2025. Data to consider: Current status: WD (last published: 11 November 2022), ED from 28 August 2025 [WPT](https://wpt.fyi/results/css/selectors?label=master&label=stable&aligned): passing tests (all tests, not sure how to restrict to level 4): Chrome: 4934, Edge: 5550, Firefox: 5592, Safari: 4898; [interop](https://wpt.fyi/results/css/selectors?label=master&label=stable&aligned&q=all(status%3Apass)): 4808 / 5679 (84.7%), 5500 / 5679 (96.8%) for [Edge and Firefox](https://wpt.fyi/results/css/selectors?label=master&label=stable&aligned&q=edge%3Apass and firefox%3Apass) Current Snapshot section: features `:dir()`, `:lang()`, and `:focus-within` in Safe to Release pre-CR Exceptions Open issues: [on GitHub](https://github.com/w3c/csswg-drafts/issues?q=is%3Aopen+is%3Aissue+label%3Aselectors-4): 128, [in spec.](https://drafts.csswg.org/selectors-4/#issues-index): 8 Summary: High interoperability, very high interoperability between two engines, though many open issues. Though as not all features are supported by browsers, maybe only the interoperable ones should be added to Safe to Release pre-CR Exceptions. Sebastian Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12713 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 2 September 2025 11:13:15 UTC