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

Re: [csswg-drafts] [css-lists-3] Should unicode-bidi / direction apply to ::marker? (#3809)

From: Mats Palmgren via GitHub <sysbot+gh@w3.org>
Date: Mon, 08 Apr 2019 14:44:28 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-480862184-1554734667-sysbot+gh@w3.org>
Fwiw, here's our [current UA sheet rule](https://searchfox.org/mozilla-central/rev/6db0a6a56653355fcbb25c4fa79c6e7ffc6f88e9/layout/style/res/ua.css#129-134) for `::marker`.

> However, unicode-bidi isn't listed in css-pseudo-4 as a valid property on ::marker.

Please just remove all of the restrictions. It's better if `::marker` behaves exactly as `::before/::after` in terms of styling/layout. It literally follows the same code path as `::before/::after` in Gecko and I see no reason to change that. You could add a note there saying "we _may_ restrict which properties applies to `::marker` in the future if it proves impossible to implement in UAs or web compat demands it", if you think it's necessary (I don't).

**Caveat**: in Gecko, you need to use the `content` property to trigger the new code path. This is a temporary implementation restriction which we intend to fix so that the legacy code path for `list-style-type/image` synthesize a pseudo content node instead and then use the new path too. (We'll fix this soon hopefully.)

GitHub Notification of comment by MatsPalmgren
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3809#issuecomment-480862184 using your GitHub account
Received on Monday, 8 April 2019 14:56:38 UTC

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