Safari is broken on purpose in a lot of ways when it comes to security, for better or for worse. I've had to do a lot of workarounds for Safari to compensate for the restrictions on cross-origin frames even though the host allows for the origin in its CSP, just as an example. Then of course there's the lack of support for WebRTC and virtually no support for PWAs. As Apple doesn't really view itself as a software company, and because they value user privacy to some extent, I don't think they care about having Safari compete with the rest of the browser market.
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.
Then of course there's the lack of support for WebRTC and virtually no support for PWAs.
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.
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.
Safari is broken in ways that don't make sense if you don't live in apple land, so I can't bother with their mess for 5 or 6% of the total browser market
most of that 2 billion is concentrated in the US and the wealthier european nation states. places with people who are educated enough to understand "this website works best on chrome" or "this browser is not supported" error messages. it's pretty easy to see where the wind is blowing
i'm living in india right now and basic websites like dominoes ordering websites glitch out on safari/iphone prompting me to switch. complaining does nothing,i've had lengthy chats with dominoes support - it's just not a priority. apple is going to pay for ignoring developing markets imo
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.