The Safari team has been killing it in interop-2022.[0] They've not only improved the most (and are currently leading) but was also way ahead on certain features like the new color spaces.

[0] https://wpt.fyi/interop-2022

> For features, that's what focusing on currently existing web is about, instead of future possible web.

The reality is, of course, much more complex.

For example, once upon a time Apple wanted web components to be declarative: https://twitter.com/rniwa_dev/status/1352322006448947203 And yet Google was "move fast and break things" and here we are 10 years later with Declarative Shadow DOM struggling to become a thing.

However, this aggressive push did surely help Google to sabotage Mozilla when they kept the abysmally slow polyfill for the deprecated v0 of Custom Components spec on Youtube for ages.

This also applies for the many, many, many features of the "future possible web" that both Apple and Mozilla increasingly object to (anything from hardware APIs to web-component-related bullcrap Chrome churns out every day it seems).