Lift restrictions for properties applying to ::marker
Categories
(Core :: Layout: Generated Content, Lists, and Counters, defect)
Tracking
()
People
(Reporter: sebo, Unassigned)
References
(Blocks 1 open bug)
Details
According to https://drafts.csswg.org/css-lists-3/#marker-properties, all CSS properties can be set on ::marker pseudo-elements and will have a computed value. And inheritable properties apply to the text contents of those pseudo-elements.
The specification only restricts, which properties actually apply to a marker box.
There's currently a pref layout.css.marker.restricted that controls, which properties apply to ::marker. Given the above, this restriction should be lifted.
There are a bunch of Web Platform Tests, which currently fail due to this restriction:
https://wpt.fyi/results/css/css-pseudo?label=experimental&aligned&q=marker
See also the discussion in https://github.com/w3c/csswg-drafts/issues/12816.
Sebastian
|
||
Comment 1•14 days ago
•
|
||
Just to be clear, not all restrictions need to be lifted.
Other properties should not have an effect on the marker box when declared directly on ::marker in the author or user origin of the cascade. UAs may either treat such properties as not applying, or enforce their value or inheritance from the originating element by setting a user-agent origin !important rule.
Firefox is basically doing something equivalent to the latter.
Description
•