What a load of BS. How can I test my website on safari without owning Apple hardware? I can't so I don't.
Safari on iOS cannot be tested without paying Apple so I generally don't for my personal stuff either.
All of that said, American developers often can't even be bothered to support characters like ñ or é, so I think it's quite reasonable to expect an EU browser to be a second class citizen for American developers. We can work around that pretty easily by simply not buying products and services that don't work well in the EU.
I welcome the Safari walled garden because if Apple have to allow chrome on ios, that's the end of any cross browser testing (and the end of Firefox)
It's the perverse incentives where companies with a captive audience that can't easily churn will be the ones that ship broken half-arsed sites and not care.
One phenomena I am seeing more that makes me boil with fury is infinite captchas in Firefox. If Firefox increasingly gets excluded "for security" then...
This is driven by enhanced tracking prevention. If you turn that off for the respective site, then it goes away.
Pretty sure I try disabling protections in such situations but maybe not. I returned to the last site that did it to me to try this out (on a different machine) and it didn't captcha me at all with protections on! Ugh.
I can't figure out if this is true. I certainly get constant captchas, but everybody else I know who uses firefox is also ad-blocking, dropping cookies, resisting fingerprinting, forging referers, downloading embedded videos, etc. etc... A lot of us look like anonymous bot traffic because we are trying to look like anonymous bot traffic. I don't know what the solution would be.
1. A form that could not find anymore a picture when they selected it from the Mac Photos app. Apparently Photos creates a temporary file that disappears before the browser submits the form, when probably reads it again from disk. No problems when the picture is loaded from a normal folder. We should read the picture into the memory of the browser and add it to the form from there, of transition to a JSON request. My customer decided that it's a niche case and it's not worth working on it.
2. A slight misalignment of an arrow and a checkbox, but that also happens in a different way with Chrome and Firefox, so there is some structural bug in the DOM/CSS of those UI elements. We're working on that.
Except those issues I can't remember any cross browser or cross OS problems in the last years. If it works in Firefox it works in Chrome and Safari too.
Arduously?
Check this very surprising thing out:
https://github.com/WebKitForWindows/WebKitRequirements/relea...
This is how Playwright has a webkit engine. An old discussion:
https://schepp.dev/posts/running-webkit-on-windows/
And this visual engine rendering compare tool leverages it:
https://github.com/niutech/splitbrowser
Separately, not sure if/when this will be a real thing for Linux:
https://www.omgubuntu.co.uk/2025/03/kag-orion-web-browser-co...
Being able to run cross-platform browsers on iOS does in fact make the very thing you're complaining about better.
I would love it if the EU did in fact force apple to release a cross-platform iOS emulator to allow web developers to properly test iOS browsers, but presumably apple would argue that there are strong technical reasons there (and the DMA differentiates real technical reasons from monopolistic arbitrary roadblocks).
For making browsers available across regions, that's very obviously not driven by strong technical reasons. Making cross-platform code has real technical burden.
Customers bought Samsung tablets to use our SaaS product. If you're in the right area of business, you can just ignore Safari.
> but presumably apple would argue that there are strong technical reasons there
They already have to make the appropriate iOS simulators and firmware for European developers. Making that available to American developers costs them nothing extra. They just don't want to.
I'd be pissed if someone did that for my browser engine of choice. Also, from what I understand, Apple still leads in accessibility, so this would be an asshole move towards consumers stuck in that ecosystem just because Google and Microsoft can't get their act together.
I read it differently. I don't think they said somehow block people from using their browser of choice, but that if you report an issue, the first thing tech support will do is ask you to use a different browser. I think it is reasonable.
A very unreasonable expectation.
@javcasas for sure it's not practical if you want to develop with it, I was more thinking of testing on preprod/prod.
But maybe ngrok can be sufficient to test your local dev from the VM?
10 cents is the smallest of the associated expenses. You are ignoring all the other expenses.
For small amounts of usage, the cheapest I’ve ever seen is $1 per hour, with a minimum spend past $30, with various further strings attached. And most are much more than that.
But it's not $1 per hour.
For smaller businesses and hobbyists it feels like expecting support for all major browsers would be discouraging in a negative way. I appreciate digital art even if it doesn’t work in my favorite browser and a shitty online menu for a food truck is better than none.
Download the windows version from their website?
If Apple doesn't want to make their browser available for other hardware that's on them and they'll suffer the consequences. Blocking other entities from making their browser available on Apple's hardware is very different.