Re:Windows 11 will respect default browser for system apps i...
by layer8 on Wednesday August 30, 2023 @08:38AM
(#37321085)
Region settings, possibly: https://www.groovypost.com/howto/adjust-region-settings-on-w...
[ Parent
| on HN ]
Re:Windows 11 will respect default browser for system apps i...
by capableweb on Wednesday August 30, 2023 @08:39AM
(#37321103)
Probably a combination of different inputs, like timezone, regional, GPS (if computer supports that) and figuring out public IP. Knowing Microsoft, they'll try their hardest to avoid flagging a computer as within EEA if they possibly could.
Re:Windows 11 will respect default browser for system apps i...
by leshenka on Wednesday August 30, 2023 @08:43AM
(#37321151)
hopefully the "inside EEA" flag will be stored somewhere in registry
Re:Windows 11 will respect default browser for system apps i...
by wistlo on Wednesday August 30, 2023 @08:47AM
(#37321188)
Or better yet, a registry flag to enable browser choice.
Re:Windows 11 will respect default browser for system apps i...
by layer8 on Wednesday August 30, 2023 @08:51AM
(#37321259)
That’s what the “default browser” setting is for. Microsoft just deliberately choses to ignore it in some parts of Windows, and instead hardcodes Edge.
Re:Windows 11 will respect default browser for system apps i...
by pluijzer on Wednesday August 30, 2023 @08:58AM
(#37321381)
I wonder how this works, if I buy a laptop in the EU as a EU citizen and travel to for example the US, I still expect them to adhere to the rules where I bought it.
Re:Windows 11 will respect default browser for system apps i...
by capableweb on Wednesday August 30, 2023 @11:02AM
(#37323241)
I don't think that's how regulations apply in general. Usually they're scoped to the geographical location + your sovereign status, but not just your sovereign status.
For example, I don't think it's realistic to expect a US citizen traveling to a EU country having to follow US regulations and laws, nor the opposite.
So I'm not sure it would apply in this case either, but I'm not even sure what regulation/law made Microsoft add this change to the update in the first place. If we can figure that out, I guess we could figure out the real answer to your question without guessing.