Re: [csswg-drafts] [css-lists] How to control the gap between the marker and the text? (#4571)

> In fact, ordered lists don't have a gap between the counter and the text

Ordered vs unordered is just an HTML concept, CSS doesn't care about that.

> It looks like as if there's another hidden pseudoelement between the marker and the text.

Not in Blink.

> `::marker` implementation is lacking in browsers

I implemented it in Blink. AFAIK only these are missing: `::before::marker`, `::after::marker`, and maybe some property that was defined to apply to `::marker` after I shipped it.

> if you compare the predefined counter styles, e.g. disc, you'll notice that implementation is not exactly the same

Yes https://drafts.csswg.org/css-counter-styles-3/#simple-symbolic: "a UA may instead render these styles using a UA-generated image or a UA-chosen font instead of rendering the specified character in the element’s own font"

> instead of overriding `disclosure-open` and `disclosure-closed`

That's because they are [non-overridable counter-style names](https://drafts.csswg.org/css-counter-styles-3/#non-overridable-counter-style-names).

> And the tests themselves are invalid

The above doesn't make the tests invalid.

> I believe it makes these markers and the default presentation useless, as you can't make them behave the same across browsers

I don't see how you reach this conclusion. Leaving some details up to the UAs doesn't make the entire thing useless. And you can always use your own counter style.

> there's no recommended way to control the gap between the marker and the text, other than adding spaces to the suffix

Well, yes, the suffix in a counter style, or the `content` property in `::marker`. If the marker has an outside position, you can also add padding to the list item to increase the separation (and possibly a negative margin if you want to move the marker instead of the contents). The point of this issue is to discuss if we need something better, and what it would be.

-- 
GitHub Notification of comment by Loirooriol
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4571#issuecomment-2323459495 using your GitHub account


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

Received on Sunday, 1 September 2024 18:54:56 UTC