3 ms·
I don't know about you, but testing on Chrome and assuming it will also work on Safari is far from "good enough" for me.
by MatthewPhillips 14y ago
I don't know about you, but testing on Chrome and assuming it will also work on Safari is far from "good enough" for me.
- darklajid 14y agoI've never been a Safari user, on any platform. Can you tell me if Safari on Windows was a reasonable way to test for Safari compatibility - or was it too far off from the 'real thing' so that you really test 'Safari on Windows or devices that weren't turned on for years' if you run it on a Windows based dev machine?
- msbarnett 14y agoTo give you an idea: Safari on Windows was pretty often criticized for having ported over the entire OS X font rendering engine (so it looked pretty wildly out of place on Windows), but that was part of what made it a fairly accurate rendition of what it looked like under OS X. There were still discrepancies even then, sadly.
- Kerrick 14y agoThat font rendering engine was the main reason I used Safari for Windows for so long. I absolutely love it.
- masklinn 14y agoOn the other hand, testing on Safari/Windows did not ensure it'd work flawlessly in Safari/OSX (still a whole lot better than taking Chrome as a good enough approximation though)
- andrewfelix 14y agoSo true. Ran into a few Mac Safari issues that weren't visible in Windows. I now run a Mac VM to test, which has the added benefit of an iOS emulator.