- From: Sebastian Zartner via GitHub <noreply@w3.org>
- Date: Wed, 17 Sep 2025 08:59:38 +0000
- To: public-css-archive@w3.org
> > implemented in all major browsers since 2020 > > WebKit doesn't support `content` nor a bunch of properties that are supposed to work: https://bugs.webkit.org/show_bug.cgi?id=204163 Interestingly, according to https://wpt.fyi/results/css/css-pseudo/parsing/marker-supported-properties.html?label=experimental&aligned&q=marker WebKit supports parsing `content` while Gecko fails a lot of those tests. Anyway, I already wondered whether I should add a note about that but then thought it's obvious from the WPTs. Though given the numbers don't fully reflect the support, I've now added a short note. Thanks for the hint! > Also the wpt link is wrong, tests are in: > > * https://wpt.fyi/results/css/css-pseudo?q=marker > > * https://wpt.fyi/results/css/css-lists?q=marker Copy & paste error. Fixed that and added the list ones. > Also see some open issues against css-lists (not all are about the pseudo-element): > > * https://github.com/w3c/csswg-drafts/issues?q=is%3Aissue%20state%3Aopen%20label%3Acss-lists-3%20%22%3Amarker%22%20in%3Atitle I've added the css-pseudo-4 tag to all that seemed related to the pseudo-element and added the URL to the description and updated the issue count. Again, thanks for the hint! Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12816#issuecomment-3302021162 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 17 September 2025 08:59:39 UTC