I said what I meant to say, I've literally drafted web standards before and Safari is often the last to implement them. I'm not talking about WebUSB or WebGoogleAnalytics or whatever

So what are you talking about? Sticky? Has? Subgrid?

Don't forget about the times where Safari implemented standards wrong, or changed the standards after the fact.

Viewport units have been around for a decade now, and Safari still can't get them right.

For example:

Let's say we want to make a chat window, where a user can type in an input field at the bottom and little message bubbles appear above. Sounds like a job for flexbox and viewport units.

Okay, we'll have one flexbox div container with it's children being the chat messages and the input which get aligned to the bottom. Now we'll position the container so it takes up the full page using viewport units (e.g. take up 100% of the viewport's width, and take up 100% of the viewport's height).

Oh no! When the user scrolled through the messages, the browser's tab bar appeared and instead of calculating that 100% of the viewport is 100% of the viewport, the viewport isn't being updated, and now the input field has been scrolled out of the page.

That's okay, we'll just use the new dynamic viewport units which specifically account for the problem that Safari had invented, and which only took 8 years to come out.

Okay looks good, time to send a message.

Oh no! When tapping on the field input, now the keyboard covers up field so we can't see what we're typing.

>_<

Good work Safari... Real good work...

When I say I want something to take up 100% of the viewport, I mean 100% of the viewport.

They spec clearly states that the keyboard is not part of the viewport. So, yeah, good work, Safari.

MediaSourceExtensions (https://caniuse.com/mediasource)is one good example of a useful API which has been supported by roughly ~every browser for years except for safari on iPhone.

On that page it says that media source was implemented in 2014, on year before Firefox and Edge.

I guess in your world "every other browser" is Chrome. And, sure enough, there are some parts of the API that are only implemented by Chromium-only browsers, and are not implemented by either Safari or Firefox.

So, what other untruths you're going to tell us?