Now that Safari supports the HTML5 date picker (since iOS 14.1 - five years ago), this is more of a meme than fact-based reasoning. Unless you believe Google including something in Chrome automatically makes it a "standard."
I have a list (unfortunately on a device I can't access now) of web standards that are supported on Safari and Firefox, but not on Chrome. I need it because one web site I work on is 100% Safari users (about 800 people), and another is mostly Android (about 70%). So I need a cheat sheet of which does what.
>Now that Safari supports the HTML5 date picker (since iOS 14.1 - five years ago), this is more of a meme than fact-based reasoning
Apple forces all browsers on iOS to use the Safari browser engine, which they intentionally hobble by not implementing APIs that other browser engines have had forever so that Apple can force developers to create native apps for iOS which Apple then can extract 30% (or whatever they decide it is today) revenue from, where they can't do that from a web application. This is one of many reasons Apple is being sued by the DOJ for antitrust violations, and one reason they got sued by the EU and lost.
Go here:
https://caniuse.com/?compare=chrome+143,safari+26.0&compareC...
Note the non-supported Safari API's, the vast majority are not web standards.
Apple forcing Safari on iOS is present day, today, not 5 years ago (but it was also 5 years ago too, ever since there was an iOS webview). If Apple doesn't want to implement it, then they shouldn't force other browser makers to use their hobbled browser engine.
Your comments are some Stockholm-syndrome level nonsense you're spouting to protect your favorite brand.
I really never commented on lock-in, even said it's fine to dislike it. You're fighting an imaginary opponent here.
I really just pointed out that Safari largely caught up on web standards. It's Google doing the whole "embrace, extend, extinguish" thing that IE pioneered by stuffing non-standards into their browser so they can lock people in.
FTFY
Without IE we wouldn't have XMLHTTPRequest, something used by practically every web developer in existence today. Innovation happens, and apparently so do walled gardens that outright forbid any competition.
It's one thing to not implement web bluetooth, web midi, and other APIs on your own browser, it's quite another to block anyone else from doing so with their web browsers. The EU thought so too and forced Apple to let other browsers use their own engines. But not in the US yet, until the DOJ completes the case against Apple.
I’d love to debate you on the rest, but it’s a debate that’s been had here at least a thousand times.
** What matters is that Apple is still blocking other browser vendors from using anything but Safari. **
The fact you can't or won't see how fucked up that is tells me everything I need to know about you.
Edit: I looked it up, and apparently its added in Safari 26!