Comment by smoldesu
3 years ago
https://caniuse.com/?compare=firefox+101,chrome+103,ios_saf+...
You can draw your own conclusions. Personally, I think the omission of the vast majority of webapp functionality (Web Bluetooth, WebUSB, WebHID, screen orientation, haptics, etc.) is a real shame, and probably what's really holding back Safari at the moment.
...but what does it matter what Apple does? People aren't angry that Safari sucks (though it certainly doesn't help), rather that they can't choose the browser they use on a device they bought with their own money. I reckon that's a valid concern, regardless of which arbitrary browser feature trinkets WebKit can collect.
A lot of these are used to fingerprint users to better track them for advertisement industry (https://www.wired.com/story/browser-fingerprinting-tracking-...)
I feel (but have no substantial reason) that the subtext of this sudden governmental interest in this issue is more so the fight between the lobbies of ad-supported tech giants (Google, Facebook) and Apple
While I agree that Safari doesn’t implement a lot of features , the intention of this post is about what features it doesn’t implement, but what standard features it doesn’t. As I recall , APIs like Web Bluetooth and WebUSB are experimental features.
Does caniuse differentiate features that are full web standards or in draft stages? I’m looking for a tool that does so but it seems none of them do.