Mostly in everything that has to do with PWAs. It’s gotten better since they introduced Web Push last year, but there’s still a lot of things it doesn’t support, like Web Bluetooth, AV1 (except for devices with hardware decoders like the 15th gen Pro iPhones), and things like mobile sensor inputs.
But also in how bad its rendering engine is. Things that work on every other platform render super weird in WebKit.
Thanks. Do you have an example of the super weird rendering? Also are none of what you’re saying here togglable in the WebKit Feature Flags to mess around with bleeding edge features?
Mostly in everything that has to do with PWAs. It’s gotten better since they introduced Web Push last year, but there’s still a lot of things it doesn’t support, like Web Bluetooth, AV1 (except for devices with hardware decoders like the 15th gen Pro iPhones), and things like mobile sensor inputs.
But also in how bad its rendering engine is. Things that work on every other platform render super weird in WebKit.
Thanks. Do you have an example of the super weird rendering? Also are none of what you’re saying here togglable in the WebKit Feature Flags to mess around with bleeding edge features?
Every time I want to use a new feature of web browsers, if support stops me from doing so, it’s always safari to blame.
What was that last or current feature you’re missing out on and what’s the use case?
I really can’t remember an example off the top of my head. Over the last 5 years it’s probably been an issue more than 20 times.