>The time for vetoing it was when it was being decided (and Apple does shoot down tons of proposals), not when everyone else already agreed is was a good idea.
But this isn't what happens. Safari is pretty good at standards (they do support BigInt and fetch). What actually happens is Google "proposes" a standard, pushes it to Chrome, then goads Mozilla and Apple into adopting it. Half of the time web developers cry about Safari not adopting Standards its because they want to adopt a experimental API that Google pushed