Geolocation API is slow to complete
Reported by
eric.and...@gmail.com,
Jun 26 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 Steps to reproduce the problem: 1. Visit this test website I made https://sparkling-saturday.glitch.me/ 2. Press the confirmation to allow the site to access your location 3. Refresh the page, and notice in the DevTools JS console how long navigator.geolocation.getCurrentPosition() takes to succeed What is the expected behavior? A Geolocation lookup that is instantaneous...but I'm not sure what a good expectation is here. What went wrong? When running this code, I notice that Geolocation takes anywhere from 2-6 seconds. 6 seconds when I hit a page cold for the first time in a while, and ~2 seconds when I hit refresh on the page. I would expect this API to resolve faster, but I am also unaware of the underlying technology that is at play. Did this work before? N/A Chrome version: 67.0.3396.99 Channel: stable OS Version: OS X 10.13.5 Flash Version: Shockwave Flash 30.0 r0 Thank you for a great browser :)
,
Jun 27 2018
,
Jul 5
Sometimes the call to navigator.geolocation.getCurrentPosition() doesn't resolve at all either.
,
Jul 6
eric.andrew.lewis@ Thanks for the issue. Able to reproduce this issue on Windows 10, Mac OS 10.13.3 and Ubuntu 17.10 on the reported version 67.0.3396.99 and the latest Canary 69.0.3483.0 as per the original comment. Attached is the screen cast for reference. This is a Non-Regression issue as this behavior is observed from M-60 chrome builds. Hence marking this as Untriaged for further updates from Dev. Thanks..
,
Jul 11
|
||||
►
Sign in to add a comment |
||||
Comment 1 by vamshi.kommuri@chromium.org
, Jun 27 2018