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.”
What you are mentioning is forcing companies to comply when selling inside the EU or California. The EU does not force companies to comply with their specifications outside of the EU. Companies simply do so because it is convenient.
The EU cannot decide how cars should be made that are sold in California. If they tried, I bet the US government would have something to say about it.
What the EU can do, is exert influence to get other governments to adopt the same rules. This already happens with a lot of countries surrounding the EU. But asking another government to adopt rules, is wildly different from forcing companies to adhere to those rules inside the borders of another government.
i understand that of course, but the EU can, for example, force products that are sold in the EU to have no developer restrictions that are not compliant with EU law
… just like it can (try) to regulate the sale of of things like conflict diamonds