Probably 2/3rds of the bugs I get are specifically related to Safari while the other 1/3rd are just general issues that affect every browser.
It's insane to me that they provide no way to possibly resolve this without going out and spending money to buy their hardware.
=> https://WebKit.org/downloads
They’re not marketed as “Safari” because Safari is part of macOS, but it’s an official build of the same rendering engine.
But unfortunately they don't provide binaries, so you have to build from source.
https://trac.webkit.org/wiki/BuildingCairoOnWindows#Download...
I'm not even using Mac OS currently, but I don't think it's Apple's job to make your web app run like on Chrome when Google is calling the shots on so-called "web standards" with tens or hundreds of new features every quarter, with necessarily surprising results. Personally, I'd find it ok if you just label your app with "Best run on Chrome" because that's the reality the web has degraded to, and the actual problem of web apps. Or deploy as Electron app on Mac OS.
Maybe Apple could provide a Mac OS + Safari VM, like MS was doing (or still is doing?) when they were producing IE. But then the question is on which machine would you be able to run those VMs given Apple is heading towards ARM-only instruction set machines. Should Apple commit to produce x64 binaries for backward-compatible emulation on historic hardware? Personally, I do like Apple's innovation where the rest of the industry is lagging behind.
[1]: https://www.xda-developers.com/safari-for-windows-editorial/