[senkora]

Yeah, this seems reasonable to me. The better thing to get annoyed at Apple for is being slow to implement web standards. I guess you could make the argument that they are choosing to work on stuff like this instead, but I think that’s a weak argument.

[paradox460]

And even then, they've made efforts to get better. Safari is starting to edge out Firefox for support of the features I actually want to use

[move-on-by]

I just want to use color SVGs as favicons. One file format- looks great on any screen at any size. But no, Safari isn’t interested in that feature.

Edit: I looked it up, and apparently its added in Safari 26!

[reaperducer]

The better thing to get annoyed at Apple for is being slow to implement web standards.

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.

[leptons]

>>The better thing to get annoyed at Apple for is being slow to implement web standards.

>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.

https://www.justice.gov/archives/opa/media/1344546/dl

[nwienert]

Maybe 5 years ago this was a true, they accelerated development and their standards support is pretty good now, better than FF. Again, not counting Chrome's "EEE" non-standard API's, they largely move fast and implement most modern ones. Some PWA stuff is missing which is valid, while Chrome is behind on a few nice design-focused standards Safari has.

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.

[leptons]

Maybe you should read the DOJ suit against Apple. It's pretty clear that one reason (among many) that Apple is getting sued is because of abusive business practices exactly as I described.

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.

[nwienert]

So you’re ignoring my entire comment and re-iterating the part I didn’t respond to.

[leptons]

Nothing in your comment makes any difference so long as Apple blocks other browser engines on iOS. I honestly don't give a fuck what they do with Safari as long as they allow real Chrome to exist on iOS, which I can then instruct my users to install because Safari is a piece of shit browser.