Jen SimmonsWeb developers, do you test your sites in Safari Beta? (On a standalone machine, automated? On your Mac?)
If not, why? Is it because installing the beta overrides regular Safari? If you could have Safari & Safari beta both at the same time, would you do so?
What do you need? Why? Share details!
westbrook@jensimmons@front-end.social Most important things is definitely support for Safari in more contexts. You can use a fork (Playwright) or a WebKit/Epiphany on Linux, but at large the inability to leverage SAFARI in enough places is a huge blocker.
Andrew Berry@jensimmons@front-end.social No, and most of our customers only care about Safari on iPhones. The lack of a real Safari for Linux (for CI) and Windows (for folks in Windows shops without Macs) is a major issue. Even in CI with Playwright using Webkit, it’s by far the slowest and flakiest browser and we often end up disabling it in tests too. (1/2)
Andrew BerryFurther, even if they want to test with Safari. they often limit it to public pages only and not authenticated experiences. Those are considered “good enough” if they work in Chrome.
It’s unfortunate, but I get it. I was a Safari user until recently, when integration issues with 1Password (fixed in 15.6 at least) drove me to another browser. (2/2)
Andrew BerryFurther, even if they want to test with Safari. they often limit it to public pages only and not authenticated experiences. Those are considered “good enough” if they work in Chrome.
It’s unfortunate, but I get it. I was a Safari user until recently, when integration issues with 1Password (fixed in 15.6 at least) drove me to another browser. (2/2)