[flagged]
Like it or not, W3C standards have always been reactive to what browsers are already doing.
And what's really remarkable about this list is that quite a few are supported on Safari on Mac, just not on iOS. Like autofocus. It's just a simple attribute you can put on an <input> tag that autofocuses that element when the page loads. It's on Mac Safari. It's on Android browsers. It's just not on any iOS browser because, you have to assume, someone at Apple held it back for not very good reasons.
Also autofocus on page load is a terrible idea on iOS as it automatically brings up the keyboard.
No one wants to switch between web pages and suddenly have to wait for the keyboard to appear each time on page load.
That's a fair statement. Conversely, why should we put up with Apple stifling the web platform? Especially when there's strong evidence to show this is motivated primarily by profit rather than the user experience [1][2].
[1] https://open-web-advocacy.org/walled-gardens-report/ [2] https://changelog.com/jsparty/316#t=00:25:59.26
Expectation on iOS is that anything that is focused you should be able to type into.
I find it absolute madness that anyone would use an API in their code which is only available on Chrome. If its not a standard which is not supported by the 4 main browsers, then its not going in my code.
It's OK to acknowledge that sometimes Google does good stuff.
And some features e.g. long lived first party cookies which are used for retargeting serve no legitimate purpose except to support advertisers.