There are over 2 billion iOS devices and every browser on iOS—Firefox, Chrome, Brave—uses WebKit.
Honestly asking...
It might seem like minutiae, but, safari also doesn't pay any attention to SVG specs. This makes the pages I build for beaver [1] like, impossible. They work beautiful in chrome; but they don't work at all in safari; and because of that, I can't really explore what potential experiences pushing the limits on SVG might have for my clients. Whatever you build has to work in all clients. It's a sad state of affairs, because if safari wasn't so far dilapidated, I would have been able to build some really impressive experiences; but, without safari support it's a no-go.
(1) www.beaver.digital
The latest version of Edge broke the "FormData" constructor. So you can't manually create FormData to post from a set of elements not already in a form element together.
And the failure is insidious, it would wipe the value, but still submit the key. Overwriting any previously saved data.
Reported it three months ago, assigned to someone, no progress.
If Edge is broken, I can't really tell beyond what I think were some quirks still present when I was trying to target it last year. It wasn't that bad, but it didn't seem like Microsoft was making as big an effort towards it as they could have.
What disappoints me is that, for reasons unknown, Microsoft didn't choose Gecko as its rendering engine, as it(and Firefox) could benefit from the extra attention and money from Microsoft.
EDIT: I initially said "Spidermonkey" when I meant to say Gecko.
From Webkit.org, June 7, 2017 [1]:
>Today we are thrilled to announce WebKit support for WebRTC, available on Safari on macOS High Sierra, iOS 11, and Safari Technology Preview 32. In this post, we will go through an overview of our implementation. We will have future posts that cover more best practices for developers.
[1] https://webkit.org/blog/7726/announcing-webrtc-and-media-cap...
For PWAs, you need Service Workers and some accompanying APIs and Safari seems to have those as well: https://webkit.org/blog/8090/workers-at-your-service/
Safari supports service workers but without support for the Web App Manifest, hence no "Add to Homescreen", PWAs are basically crippled on iOS.
https://webkit.org/status/#specification-web-app-manifest https://developer.mozilla.org/en-US/docs/Web/Manifest
Android Browser, Chrome, and Firefox all support this feature at this point but not Safari or anything that uses WebKit. So while service workers are supported on iOS Safari, PWAs are relegated to being mere cached webpages. The manifest is probably more important than service workers because without it all you have is a webpage that is treated no differently from other web pages. A progressive web app is supposed to share characteristics with normal apps by definition and be recognized as such by the browser, which is still not the case in Safari.
So yes, there is still virtually no support for PWAs. There would be partial support if some manifest features were implemented, but currently it's not supported at all.
Moreover, it's irrelevant to non apple people
This ain’t your father’s Safari web browser: https://webkit.org/status/#?status=under%20consideration,in%...
There’s a lot of stuff that’s already supported in the released Safari and lots more stuff in development and being considered.
Are you equating "apple land" with increased privacy for your users, then disregarding it?
