W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2019

Re: [csswg-drafts] [css-lists] How should spaces be treated in markers? (#4448)

From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
Date: Sun, 10 Nov 2019 16:41:18 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-552211412-1573404077-sysbot+gh@w3.org>
> although Safari currently doesn't support @counter-style yet, bullets are separated from the body with two spaces

Actually it's a bit more complicated, and depends on `list-style-type`. But in most cases WebKit uses a separation of 1 space plus 1/3 of the font ascent.

> Firefox, Chrome and Safari implement `counter-style: disc` with some sort of custom circle [...] Effectively, this means `font-family` isn't useful

You can force the U+2022 character with `list-style-type: "\2022  "`. Firefox has supported it for a long time since version 39, and recently I have implemented it for Chromium 79 and WebKit.

> there seems to be relatively little appetite (for both the specification and implementations) to move forward

Well, WebKit shipped a limited version of ::marker 2 years ago, more recently Firefox shipped it completely, in Chromium I have implemented the WebKit behavior behind a flag and I'm working on completing it. This allows marker customizations, and will be much more powerful when we start accepting more properties in it. So things are moving forward, though it's true that outside positioning is heavily underspecified.

-- 
GitHub Notification of comment by Loirooriol
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4448#issuecomment-552211412 using your GitHub account
Received on Sunday, 10 November 2019 16:41:20 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:56 UTC