- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 14 Jan 2026 16:59:52 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-2026][selectors-4] Add features from Selectors 4 to Safe to Release Exceptions`, and agreed to the following: * `ACTION: Review https://github.com/w3c/csswg-drafts/pull/4212` * `RESOLVED: As astearns described above` * `ACTION: astearns to post the list to the issue` <details><summary>The full IRC log of that discussion</summary> <fantasai> SebastianZ: In preparation for publishing CR, already moved things without great interop to L5<br> <fantasai> SebastianZ: The ones that I do think should be added to Safe to Release exceptions are ones listed in the issue<br> <fantasai> SebastianZ: Some don't have many tests or still have open GH issues<br> <fantasai> fantasai: If zero spec issues and implemented, should just go in<br> <fantasai> SebastianZ: [summarizes]<br> <fantasai> florian: lang tag is in a weird state. I made an exploratory PR, and then somebody merged it<br> <fantasai> florian: Merging it was premature. Open issue discussing that, but haven't been touched in a long time.<br> <fantasai> astearns: let's discuss those with open issues or no toests<br> <fantasai> fantasai: I suspect some of these might have tests but not tagged correctly<br> <fantasai> SebastianZ: I searched the repo for the keyword<br> <fantasai> SebastianZ: More important is how many issues<br> <fantasai> fantasai: :scope is implemented across browsers and fairly interoperable, so seems fine<br> <fantasai> astearns: So add scope, add defined, focus-visible has some issues<br> <fantasai> fantasai: I think these are all clarifications.<br> <fantasai> astearns: Interop is not great either<br> <fantasai> fantasai: so skip this one<br> <fantasai> astearns: keep dir, any-link, open, popover-open, modal, fullscreen<br> <fantasai> astearns: no tests for picture-in-picture<br> <fantasai> SebastianZ: so let's skip<br> <fantasai> astearns: also read-only?<br> <fantasai> SebastianZ: read-write has tests but read-only not<br> <fantasai> astearns: if just a lack of tests, can come back add later<br> <fantasai> fantasai: I think we keep both. From spec perspective should be well-defined<br> <fantasai> astearns: so keep placeholder-shown, skip autofill because not test<br> <fantasai> astearns: keep default, skip indeterminate<br> <fantasai> astearns: keep valid, invalid<br> <fantasai> astearns: skip in-range and out-of-range for lack of tests<br> <fantasai> astearns: keep required and optional<br> <fantasai> astearns: keep user-valid and user-invalid from spec issues<br> <astearns> skip keep user-valid and user-invalid from spec issues<br> <fantasai> fantasai: We should put the :indeterminate issue on the agenda<br> <fantasai> astearns: lang was in weird state?<br> <fantasai> florian: We have an issue with interesting discussion and a PR that was merged prematurely<br> <fantasai> florian: maybe we should revert that<br> <fantasai> fantasai: and maybe we should put that issue on the agenda at the F2F<br> <fantasai> florian: need i18n folks<br> <fantasai> fantasai: We can invite them to attend<br> <fantasai> https://github.com/w3c/csswg-drafts/pull/4212<br> <fantasai> ACTION: Review https://github.com/w3c/csswg-drafts/pull/4212<br> <fantasai> florian: Premise of this is that language tags are canonically known to be the same thing. Should we make them match.<br> <fantasai> astearns: Selector lists in :nth-child and :nth-last, issue seems not blocking<br> <fantasai> astearns: so let's add those<br> <fantasai> astearns: to rough interop<br> <fantasai> fantasai: Anything else in the spec to analyze?<br> <fantasai> SebastianZ: Resource State Pseudo-classes<br> <fantasai> SebastianZ: maybe :empty<br> <fantasai> SebastianZ: It was part of L3<br> <fantasai> fantasai: but definition changed in L4<br> <fantasai> florian: Spec and implementations are not aligned<br> <fantasai> RESOLVED: As astearns described above<br> <fantasai> ACTION: astearns to post the list to the issue<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12797#issuecomment-3750582197 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 14 January 2026 16:59:53 UTC