It seems time again to remind everyone not to use ARIA `menu` roles for web site navigation:
adrianroselli.com/2017/10/dont…
From a technical perspective, there is no such thing as “dropdowns”:
adrianroselli.com/2020/03/stop…
That imprecise terminology leads to more miscommunication between sales folks, designers, and devs than is necessary. Then weird stuff gets built from scratch instead of leaning on existing patterns.
You should dismiss articles that conflate the two.

Seirdy
in reply to Seirdy • • •Oliver Hunt
in reply to Seirdy • • •I mean that is the point of open source :)
But you also need to consider how much of that is because chrome shipped those features and therefore everyone else had to as well - Mozilla does not have the money to compete there even before its slow motion implosion
For everyone else it’s just time - plenty of these things are *huge* amounts of work, and insanely complex, and the “standard” is pretty much “whatever Google implemented”
Seirdy
in reply to Oliver Hunt • • •@ohunt Color space processing, cross platform GPU-accelerated 2d graphics, and brotli compression are things that aren’t necessary to use websites but all browsers chose to ship, and they chose Chromium’s implementations. Firefox already had other 2d backends but switched to Skia. HDR in particular is an OS feature that all programs capable of playing video and showing images are generally expected to support, and that means handling complex color metadata.
This is not the case for most examples I cited; the first sentence of the post set the scope to exclude Web standards. I was describing libraries chosen by browsers.
Multiple implementations of WebP, Brotli, and others exist; most of them aren’t browser-grade implementations. Tons of implementations of TLS 1.3 exist, but Apple (and AWS, and Cloudflare, and several others) switched to Google’s BoringSSL over popular alternatives like OpenSSL, LibreSSL, Mozilla’s NSS, and GnuTLS.
JPEG-XL has a very popular independent Rust implementation which Mozilla is not considering, in favor of one supplied by Chromium which doesn’t even support JXL right now.
None of the Chromium-inspired security improvements in Firefox are necessary to render web pages or implement standards.
Part of the point of my post was to show how reality isn’t as simple as the popular “everybody has to do what Google says because it has market share” narrative, or the “if Mozilla had an alternative to Google’s revenue it would be truly independent” narrative. Browser vendors do have choice when picking libraries that implement features or deciding on security architecture improvements. They tend to pick what Chromium has done even when given feature-complete choices because they find the Chromium options to be best.
I agree with you when it comes to Web standards, though. But this post wasn’t about standards.
alarmed feet operative: kimothy siddon
in reply to Seirdy • • •Seirdy
in reply to alarmed feet operative: kimothy siddon • • •picturefallbacks in Lockdown Mode so I wouldn’t recommend using it.Seirdy
in reply to Seirdy • • •mona 🌺
in reply to Seirdy • • •Seirdy
in reply to mona 🌺 • • •