The Register has learned from those involved in the browser trade that Apple has limited the development and testing of third-party browser engines to devices physically located in the EU. That requirement adds an additional barrier to anyone planning to develop and support a browser with an alternative engine in the EU.
It effectively geofences the development team. Browser-makers whose dev teams are located in the US will only be able to work on simulators. While some testing can be done in a simulator, there’s no substitute for testing on device – which means developers will have to work within Apple’s prescribed geographical boundary.
… as Mozilla put it – to make it “as painful as possible for others to provide competitive alternatives to Safari.”
trade agreements likely don’t cover this though
and sure there might be diplomatic pushback, but… is that really going to happen?
the EU already forces companies to make products to certain specifications if they want to be sold in the EU… as does the US and most other countries, and California in the US tends to set the standard that everyone else lives by
countries “invade” the autonomy of other countries’ markets all the time. the US is the worst offender. this is kinda the reason the EU exists: to have the power to force things to happen that is “outside” their jurisdiction
apple doesn’t have to comply. they don’t have to sell iphones in the EU. they’re making a choice