Bug 204163 - list ::marker should accept content, and several writing-mode related properties
Summary: list ::marker should accept content, and several writing-mode related properties
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: Safari Technology Preview
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2019-11-13 10:35 PST by Miriam Suzanne
Modified: 2021-01-05 15:27 PST (History)
7 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Miriam Suzanne 2019-11-13 10:35:10 PST
Safari seems to support the `::marker` selector, but only for styling `color` and `font` properties. According to the specification (https://drafts.csswg.org/css-pseudo-4/#marker-pseudo - fully implemented in Firefox), support should also include:

- `content`
- `direction`
- `text-combine-upright`
- `unicode-bidi`

I'm not qualified to comment on the last two, but neither `content` nor `direction` is supported at this point. See my example on codepen: 

https://codepen.io/mirisuzanne/pen/bGGmdpm
Comment 1 Radar WebKit Bug Importer 2019-11-16 15:45:50 PST
<rdar://problem/57257364>
Comment 2 Oriol Brufau 2019-11-18 10:57:47 PST
Also the font-kerning property.

Once I finish the implementation of ::marker in Chromium, I can try to port patches into WebKit.
Comment 3 Mihai Parparita 2020-10-21 16:35:20 PDT
Daniel: it looks like you added support for ::marker (with https://trac.webkit.org/changeset/22020) -- is this an expected limitation?
Comment 4 Daniel Bates 2020-10-21 18:17:26 PDT
I added ::marker support. What is the question?
Comment 5 Mihai Parparita 2020-10-22 10:07:45 PDT
(In reply to Daniel Bates from comment #4)
> I added ::marker support. What is the question?

The lack of support for some the properties listed at https://www.w3.org/TR/css-lists-3/#marker-properties, especially `content`.
Comment 6 Daniel Bates 2020-10-22 23:31:51 PDT
(In reply to Mihai Parparita from comment #5)
> (In reply to Daniel Bates from comment #4)
> > I added ::marker support. What is the question?
> 
> The lack of support for some the properties listed at
> https://www.w3.org/TR/css-lists-3/#marker-properties, especially `content`.

Simple answer: they weren't in the draft at the time I implement it. I implemented Editor's Draft, 24 July 2017.
Comment 7 Daniel Bates 2020-10-22 23:39:34 PDT
Just for me, closest I could find was 07/26/2017: <https://github.com/w3c/csswg-drafts/blob/d0f08fdb814ca1edab5281ec54b3d4be478d9cd4/css-pseudo/Overview.bs>
Comment 8 Ted Whitehead 2021-01-05 14:11:08 PST
Hi there, was just wondering if there are plans to implement `content` in a future release. 

FWIW, none of these sites mention `content` as not being supported in Safari (which obviously isn’t your fault, but added to my confusion until I found this ticket).

- https://caniuse.com/css-marker-pseudo
- https://developer.mozilla.org/en-US/docs/Web/CSS/::marker#Browser_compatibility
- https://web.dev/css-marker-pseudo-element/#browser-compatibilty

Thanks!
Comment 9 Ted Whitehead 2021-01-05 15:27:49 PST
FYI, for anyone who stumbles across this in the future, one of the reasons why `content` is so helpful is because the old technique of setting `list-style: none` and using `:before` causes issues with VoiceOver on Safari (see https://www.scottohara.me/blog/2019/01/12/lists-and-safari.html).