Re: [csswg-drafts] [css-2026][css-pseudo-4] Add `::marker` to Safe to Release Exceptions (#12816)

The CSS Working Group just discussed ``[css-2026][css-pseudo-4] Add `::marker` to Safe to Release Exceptions``, and agreed to the following:

* `RESOLVED: Add ::marker to safe-to-release`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Sebastian: fantasai asked to include this in the exceptions<br>
&lt;fantasai> SebastianZ: It's 74% interop, and still about 9 issues or 11 issues if counting ones in the spec<br>
&lt;fantasai> SebastianZ: Idk if fine to release?<br>
&lt;astearns> fantasai: people have already released it<br>
&lt;astearns> fantasai: basic stuff works<br>
&lt;astearns> fantasai: if the question is do you support this, the answer is yes<br>
&lt;astearns> fantasai: we’ll add more details<br>
&lt;astearns> fantasai: but the fundamental thing is working<br>
&lt;astearns> fantasai: and you can ship it<br>
&lt;fantasai> SebastianZ: Support in Firefox is mostly hidden behind a preference<br>
&lt;fantasai> SebastianZ: Filed an issue about that<br>
&lt;fantasai> SebastianZ: Oriol also added lots of tests<br>
&lt;fantasai> SebastianZ: WebKit has a different issue<br>
&lt;fantasai> fantasai: Safe to release doesn't mean it's interop everywhere. It means the spec is solid enough that browsers should implement *and ship* it<br>
&lt;fantasai> SebastianZ: open issues mostly about adding more properties<br>
&lt;fantasai> fantasai: adding more features to the feature<br>
&lt;fantasai> RESOLVED: Add ::marker to safe-to-release<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12816#issuecomment-3750358892 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:17:43 UTC