Re: [csswg-drafts] [css-pseudo][css-lists] Allow `counter-*` and `quotes` in ::marker (#5265)

The CSS Working Group just discussed `https://github.com/w3c/csswg-drafts/issues/5265`, and agreed to the following:

* `RESOLVED: allow counter and quotes properties in ::marker, revisit later if there are a lot of problems`

<details><summary>The full IRC log of that discussion</summary>
&lt;ntim> topic: https://github.com/w3c/csswg-drafts/issues/5265<br>
&lt;ntim> github: https://github.com/w3c/csswg-drafts/issues/5265<br>
&lt;ntim> oriol: In the marker pseudo, we restrict which props that can be used, because layout is special, and we wanted to avoid browsers doing random things. but there are properties like counter that affect only style and not layout.<br>
&lt;ntim> ... I have been using it in counter, which is convenient<br>
&lt;ntim> ... also you can use open-quote/closed-quote in content to increase the quotes, but you can't increase the counters, or the use the symbols increased by the quotes<br>
&lt;ntim> fantasai had mild objection<br>
&lt;TabAtkins> +1<br>
&lt;ntim> oriol: I think we should just allow it<br>
&lt;ntim> fantasai said she had opinions on this issue<br>
&lt;ntim> sakhapov: Is the ordering relative to ::before defined?<br>
&lt;ntim> oriol: yes<br>
&lt;emilio> q+<br>
&lt;fantasai> I was concerned that people will get confused about what the counter increment is doing<br>
&lt;fantasai> and not get the results they're expecting<br>
&lt;ntim> TabAtkins: It's a mystery for me why ::marker pseudo-elements are not fully styleable, but fantasai had opinions<br>
&lt;TabAtkins> people do that with ::before today and it does indeed work reasonably<br>
&lt;ntim> emilio: Isn't that because the ::marker layout is not defined?<br>
&lt;ntim> oriol: but counters don't affect layout<br>
&lt;emilio> s/::marker layout/outside-marker layout<br>
&lt;ntim> ntim: can't counters affect layout?<br>
&lt;ntim> oriol: maybe we should leave it for later if fantasai is strongly opposed<br>
&lt;emilio> emilio: they affect layout but anything you can put with text you can put on a counter<br>
&lt;fantasai> it's mainly we don't know how the counter is laid out, but to the extent that it contains text it's fine<br>
&lt;ntim> astearns: i know you said this is mostly a convenience because you can work off the element itself<br>
&lt;ntim> oriol: for most cases yes, but &lt;describes cases><br>
&lt;ntim> oriol: i have a ::before pseudo, increment the counter, and print it with content, I should be able to do the same in ::marker<br>
&lt;astearns> fantasai: would you object to us resolving to allow this, or is it more a minor concern<br>
&lt;ntim> oriol: I thought that it was more straightforward than expected<br>
&lt;fantasai> minor concern, just want to be sure we're not causing more problems than we solve<br>
&lt;ntim> PROPOSED: allow counter and quotes properties in ::marker, revisit later if there are a lot of problems<br>
&lt;ntim> fantasai: ^<br>
&lt;ntim> objections?<br>
&lt;ntim> RESOLVED: allow counter and quotes properties in ::marker, revisit later if there are a lot of problems<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5265#issuecomment-3531669680 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 14 November 2025 08:57:57 UTC