[doctorfoo]

You still can't use a non webkit browser though. It's Internet Explorer levels of non-competition. I would love to be able to say to my users, when they experience an issue with Safari - "you can try a different browser". But I can't because the same issue will be present in Chrome.

[brorfred]

But that's what you a developer want, not necessarily the users. I'm extremely happy that you can't tell me to use another browser and have to fix your code for Safari instead. I think that you have a right to decide which browser I can use, even if I'm your costumer. I knew the rules when I bought my iPhone and had to accept them, even if it means only using webkit. Being forced to switch to Chrome when using a specific website just because the developer didn't feel like making it work in Safari is very annoying on the Mac and would make me go nut on the phone.

[doctorfoo]

It's not "fix my code" when Safari doesn't even support the feature or it's simply broken - or most annoyingly, it works one day and breaks with an update. (See: webrtc stuff) You might have known the rules, but most users don't. Plenty will come to me saying they've tried both Safari and Chrome and that it won't work in either, indicating they have no knowledge of webkit.

Android also randomly breaks things now and then, but I can at least direct users to Firefox, which never seems to have any problems.

Please understand redirecting users to another browser is only ever a last resort. If I can fix the code I will, but sometimes something just stops working and I can't even reproduce it.

...and I have a teacher who is relying on my app for their classes this week and "try firefox" could save them...