I know people like to complain about Safari, but:

1. It’s absolutely common to ask developers for a minimal repro case in a bug report.

2. There are four major Safari releases under 15.x.

3. Apple OS upgrades, especially iOS, are as close to total as one could imagine. The overlap between people who buy iPhones and people who go out of their way to turn off OS upgrades is really small.

I want Apple to stop tying (some) Safari releases to OS upgrades, but this honestly feels like you’re tired and it’s been a long day, and you could use a break. Take the night off. Safari will still be imperfect but improving tomorrow, even if it’s not at the pace we’d prefer.

I want Apple to stop restricting third-party browsers on iOS. MacOS Safari has the same WebGL bugs, but our game's Desktop client uses a WebView under our control & versioning that isn't Safari, and so doesn't have the bug.

If iOS had the same capabilities, I wouldn't care at all if Safari introduced bugs, since it wouldn't break our product.

This isn't the first, or second, or third time that Apple has shipped broken stuff in Safari on iOS which broke our product. I've been dealing with this for years, and it's not getting any better. I'm absolutely frustrated about this, but when I spend time honing in patches for Safari regressions & Safari just ships more regressions, it's hard not to be frustrated.

[1] https://twitter.com/jensimmons/status/1491064075987873792

Random rendering glitches/disappearing-reappearing dom elements.

Impossible to debug without Mac and no problems in any other browser.

Seriously frustrating.

Happens on latest Safari on MacOS, too: https://cdn.discordapp.com/attachments/476502698066182179/95...

I'm not sure if the video represents what's going on perfectly, but it appears like maybe it's reading old data from an improperly cleared framebuffer or something?

a side question, how do you make a bug report on Safari? I've found FF and Chrome easy enough, but when I went to look for making one on Safari about a year ago I decided screw it, it seemed hard to find where to start (by googling at any rate)

When people want to get their work done, opening another browser while the original one is being fixed (which might take a couple weeks), for certain applications, is extremely reasonable for business people just trying to get their work done.

This foundation is provided by browsers and is also broken by browsers. If safari's foundation is broken then safari is the one not fulfilling that fundamental promise, not the websites now broken. So yes, don't use a browser if it doesn't work.

Before Opera gave up and became another Chrome reskin, there were plenty of sites that didn't work for me until I set the user agent to match another browser.