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: Mike Bremford via GitHub <sysbot+gh@w3.org>
Date: Sun, 10 Nov 2019 11:41:53 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-552186940-1573386112-sysbot+gh@w3.org>
Markers are separated from the body of the list with white-space. If you collapse that away by default, a space character in `counter-suffix` becomes useless. At the very least you're going to have to redefined the default value of `counter-suffix` to '\00A0', and if users are setting their own `counter-suffix` then things will probably break.

(Incidentally, although Safari currently doesn't support `@counter-style` yet, bullets are separated from the body with two spaces.)

Re. the marker alignment, you've already got https://drafts.csswg.org/css-lists-3/#marker-side which allows a little control. @MatsPalmgren, does this cover the case you had in mind?

My main concern with block-axis marker positions, multi-line markers etc is that the css-lists modules seems to have had considerably less love than it deserves. List bullets were first described in HTML 1, and from what I can see browsers haven't changed much in the way they position them since then.

* Only Firefox is shipping support for `@counter-style`
* Firefox, Chrome and Safari implement `counter-style: disc` with some sort of custom circle rather than the U+2022 bullet character suggested (although not required) in `css-counters-3`. Effectively, this means `font-family` isn't useful with `counter-style: disc`. Same for circle and square.
* list markers do contribute to the height of their corresponding list body, but the exact mechanism for this still isn't defined and varies across browsers (see https://jsbin.com/sasuzig/edit?html,output). This behaviour is different to a regular `inline-block`

My point is there seems to be relatively little appetite (for both the specification and implementations) to move forward. For that to change, I'd be inclined to severely limit the scope of what markers can do - at least for `css-lists-1`.

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

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