Geolocation is timing out (again) in both Chrome Stable and Canary

[Zac Spitzer]

Geolocation requests have been timing out (Australian GMT +1100 in Canary for several few weeks now)

Now Chrome Stable is also throwing timeouts or returning really inaccurate results (i.e 9596m accuracy)

I've tried to reached out to quite  a few people and it's been impossible to get this addressed, I get canary isn't 

as important as stable, but now stable is failing too and nobody seems to care enough to fix it?

Being the world's most popular browser vendor brings responsibility?

https://bugs.chromium.org/p/chromium/issues/detail?id=753242

you can play with this test harness to see the problems

https://output.jsbin.com/nupuyo

[Colin Blundell]

Hi,

Thanks for the bug report! I did some digging and reported what I believe to be the underlying issue on the newer bug that you filed for this issue. That investigation should move along now.

Thanks,

Colin

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/91261778-0d57-4ff5-b122-9b0af0745a58%40chromium.org.

[Zac Spitzer]

thank you Colin! 

as i noted in the issue, i think this bug might be related 

when Geolocation unavailable, both TIMEOUT and POSITION_UNAVAILABLE are fired

https://bugs.chromium.org/p/chromium/issues/detail?id=542923

[Zac Spitzer]

So the outcome is, yeah there are some underlying problems, but WONTFIX maybe use watchPosition?