Here's the list, prefixed by the year that these features shipped to stable in Chromium:

2023: WebGPU
2020: SVG Favicons
2023: HDR Images
2024: CSS Anchor Positioning
2023: CSS text-wrap: pretty
2025: CSS progress() function
2023: Scroll-driven Animations (finally!!!)
2020: Trusted Types
2021: URL Pattern API
20XX: WebAuthN Signal API
2020: WritableStreams for the File System APIs
late 2023: Scroll Margin for Intersection Observers
2025: CSS Logical Overflow (overflow-block and overflow-inline)
2024: CSS align-self and justify-self in absolute positioning
2025: a subset of Explicit JavaScript Resource Management
2021: AudioEncoder & AudioDecoder for WebCodecs
2020: RTCEncodedAudioFrame & RTCEncodedVideoFrame serialisation
2024: RTCEncodedAudioFrame & RTCEncodedVideoFrame constructors
2018: PCM format support in MediaRecorder
2017: ImageCapture.grabFrame()
2017(?): SVG pointer-events="bounding-box"
2015:

Safari at WWDC '25: The Ghost of Christmas Past - Infrequently Noted

And those are just the technical obstacles that Apple has put up. The proposed contractual terms (pdf) are so obviously onerous that no browser vendor could ever accept them, and are transparently disallowed under the DMA's plain language. But respecting the plain language of the law isn't Apple's bag.

All of this is to say that Apple is not going to allow better browsers on iOS without a fight, and it remains dramatically behind the best engines in performance, security, and features. Meanwhile, we now know that Apple is likely skimming something like $19BN per year in pure profit from it's $20+BN/yr of revenue from its deal with Google. That's a 90+% profit rate, which is only reduced by the paltry amount it re-invests into WebKit and Safari.

Don't fall for it. Ignore the gaslighting. Apple could 10x the size of the WebKit team without causing the CTO to break a sweat, and there are plenty of great browser engineers on the market today. Suppressing the web is a choice — Apple's choice — and not one that we need to feel gratitude for.

I think it's time to accept that Apple's really not interested in supporting the web as anything other than "that other place" which is Google's space, which we've already monetized to near 100% profitability.

And that's a bummer. I know some excellent developers in Safari and WebKit who'd love more investment from our leadership at Cupertino. Honestly, these are things that make me want to choose any other browser other than Safari. Except they have a lock on it in iOS. Which is why I continue to be glad that I primarily use a Mac and not iOS.

I will also predict this much - if it's possible at all - I would imagine Chrome doing its best to bring blink and chromium to iOS and honestly doing a better job being a browser there.