They are late to the game as always. It seems like Chromium and Firefox are the first to implement, and Safari is consistently last. There are a few standards that Safari has been first to, but it is the exception.
Meanwhile, on interoperability[1], Firefox and Safari are currently at 84, while Chrome is at... 75. Once they update with this new release, Safari should climb to 89[2].
Being first to things isn't always the great thing you're suggesting, if those things aren't actually being asked for--or wanted.
0. https://lists.webkit.org/pipermail/webkit-dev/2021-March/031...
Also, it's terrifying because it's just one of hundreds of standards that WebKit (and Firefox) might not have the time and resources to fight.
Chrome ships hundreds of new web APIs a year. Most of them are Chrome-only non-standards. Firefox and Safari are more closely aligned: https://web-confluence.appspot.com/#!/confluence
Edit: Safari also has no support for CSS counter styles or CSS paged media while Chrome and Firefox have at least partial support. Again, those don't seem particularly consequential features for moving web design forward.
https://caniuse.com/?compare=chrome+106,safari+16.0,firefox+...
When I read this, I turned on css counter styles on my iPhone:
Settings > Safari > Advanced > Experimental features.
There are a lot of in-development web features that can be enabled.
Some CSS features can be used even without widespread browser support because the content's meaning isn't changed in browsers that don't support the feature; border-radius is a classic example. For something like CSS counter styles, if an ordered list is equally well-understood with the default numbers or the custom styles, they can be fine but it's easy to think of examples where meaning would be lost without the counter styles.
I didn't claim this was a supported feature, just that it wasn't accurate to suggest that WebKit has no support for some of these features that seem to be missing. They are being worked on and will be turned on by default pretty soon.
Being available as an experimental feature does not mean its release is imminent, there are ones that have been there for years. Thankfully, it’s not like they’re in a queue, some are released after only a few months.
Or alternatively actually answer the question like an adult rather than parroting the standard Apple hates the web nonsense.
In case nobody noticed, the WebKit team kicked ass by shipping a ton of new features this year:
* dialog element
* lazy loading
* inert
* :has() pseudo-class
* new viewport units
* Cascade Layers
* focus visible
* accent color
* appearance
* font palettes for color fonts
* BroadcastChannel
* Web Locks API
* File System Access API
* enhancements to WebAssembly
* support for Display-P3 in canvas
* additions to COOP and COEP
* container queries
* subgrid
* web push
* shared workers
* CSS Offset Path
* AVIF
* Passkeys