Forum Discussion
Geolocation wrong (really wrong) in Edge but correct in Chrome
This is probably a Windows 10 API problem not an Edge issue, but geolocation is wrong - usually really, really wrong - in Edge... while Chrome gets my location dead-on. On the same computer. At the...
I didn't want to create a new post but this is definitely NOT a Windows specific problem but instead an EDGE specific problem.
I'm on a Macbook Air M1 using Edge Version 92.0.902.73 (Official build) (arm64) and my location is incorrect in google maps and waze live map
If I use Safari my location is dead on. Definite bug in microsoft edge
Both Chrome and Edge use the Windows Location Services endpoint for geolocation through the navigator.geolocator js api.
Edge obeys the Windows Location Privacy settings and Microsoft Store registered app consent store permissions. Chrome, which is not a MS store app, doesn't honor any of that. Just the site permissions.
So for Edge make sure the "Allow apps to access my location" option is on and if you are in an enterprise environment have your guys look up the admin templates for a GPO push.
That being said... The way the js navigator object works is mysterious. Sometimes I have observed the opposite. Chrome failed while Edge worked. Both scenarios with a geowatcher in high accuracy mode.
In other scenarios, with all these settings on just right, Chrome works but both Edge and a Powershell script using a geowatcher instance were BOTH WRONG.
Premiere support still hasnt got an answer for me on that one. Its going to take me a while to get in contact with the product group.
Edge obeys the Windows Location Privacy settings and Microsoft Store registered app consent store permissions. Chrome, which is not a MS store app, doesn't honor any of that. Just the site permissions.
So for Edge make sure the "Allow apps to access my location" option is on and if you are in an enterprise environment have your guys look up the admin templates for a GPO push.
That being said... The way the js navigator object works is mysterious. Sometimes I have observed the opposite. Chrome failed while Edge worked. Both scenarios with a geowatcher in high accuracy mode.
In other scenarios, with all these settings on just right, Chrome works but both Edge and a Powershell script using a geowatcher instance were BOTH WRONG.
Premiere support still hasnt got an answer for me on that one. Its going to take me a while to get in contact with the product group.