To elaborate on my hostility against WebKit: WebKit does nothing but get in my way whenever I work on literally any website.
When I rewrote nouveau's website in late 2023, it worked perfectly fine on Firefox (Gecko) and Chromium (Blink), but was broken on Epiphany/Safari (WebKit). The logo, which is an SVG, would not adapt to dark style, because, to this day, WebKit still does not support prefers-color-scheme in SVGs. So, as a workaround, instead of having one SVG file for both color schemes, we have one SVG file for light style, and one for dark style. Edit: This feature is currently considered nonstandard and is only written as a draft. WebKit behaves appropriately, see: estradiol.city/@ity/1150068605…
Another example: On my website, some elements are intentionally made to be unselectable using user-select: none;, such as the command-line decoration and the “Table of Contents” text, but on WebKit, these elements continue to be selectable because it does not properly support the user-select property. And no, using the vendor prefix is completely unacceptable, especially considering that it behaves differently.
Lastly, WebKit does not yet fully support the ::marker pseudo-element. This means, in my articles, numbered list items in the table of contents are completely wrong and don't represent the same numbers as headings.
Apple has consistently proved that they don't care about WebKit, because otherwise browsers like Safari and Epiphany would have worked as well as they do on Firefox and Chromium. There's absolutely no reason to force WebKit onto iOS and iPadOS if they're not even willing to invest in WebKit. Likewise, Apple employees working on WebKit should really stop calling themselves “WebKit evangelists” if their inferior engine regularly gets in developers’ way. So yes, WebKit sucks, and this is 100% on Apple. I don't care about being harsh. Apple is a multi-trillion dollar company, most of which came from exploiting people. The least they can do is invest in their projects.
For clarity, my hostility towards WebKit is purely targeted at Apple's lack of involvement with WebKit, not the browsers using it.
#WebKit #Apple #iOS #iPadOS #WebDev #Web #Safari
The ::marker CSS pseudo-element selects the marker box of a list item, which typically contains a bullet or number. It works on any element or pseudo-element set to display: list-item, such as the and elements.
MDN Web Docs
That's not normative, that's descriptive of Firefox & Chromium behavior (the purpose of mdn is to be descriptive rather than normative, unlike the specifications themselves)MDN even warns that "Respects color-scheme inherited from parent" is "non-standard" and to "Expect poor cross-browser support"
The feature itself is listed as "Full support" for Safari/WebKit on that site.
The feature is also considered "unfinished" by W3C, and W3C in the specification warns that
Information about a user can be used as an active fingerprinting vector. Analysis of impact pending, more information to be provided before spec is published.
User agents and developers implementing this specification need to be aware of this vector and take it into consideration when deciding whether to use the feature. Specifically prefers-reduced-motion, prefers-color-scheme and prefers-reduced-data are currently of concern for exploitation.
W3C further comments on the specific feature that
[css-mediaqueries] Should prefers-color-scheme in SVG images be context-dependent?
RESOLVED: Have prefered-color-scheme reflect 'color-scheme' on the embedding element in the embedding document, to the extent acceptable from security standpoint (pending security review)
There seems to be a draft asking for it in "Secure Animated mode" -> github.com/w3c/csswg-drafts/co…
Which has not made it to the current latest Working Draft of MQ5 (w3.org/TR/mediaqueries-5/), and is only available in the Editor's Draft (drafts.csswg.org/mediaqueries-…)
MQ5 itself is not finalized and is very much experimental.
This has been okayed into being merged into WebKit at 2022 by one of the WebKit maintainers github.com/w3c/csswg-drafts/is…
I have no idea what policy WebKit has for standards, but the only standard it seems to violate is one that begins with this statement:
This is a public copy of the editors’ draft. It is provided for discussion only and may change at any moment. Its publication here does not imply endorsement of its contents by W3C. Don’t cite this document other than as work in progress.
So while it is certainly dumb that it has not been fixed yet, it feels a bit of a stretch to call it a violation of web standards, imo.
I wonder how difficult it is to fix, I've been meaning to try to get into WebKit stuff 
Consider this test-case: for (let img of document.querySelectorAll("img")) { im...
emilio (GitHub)
