HTML5 Geolocation method getCurrentPosition returns cached coordinates
Reported by
akriz...@block.si,
Oct 29
|
||
Issue descriptionGoogle Chrome 69.0.3497.120 (Official Build) (32-bit) Revision 82a246f0f3c05b70641ab513b5fd749c1c62e19d-refs/branch-heads/3497@{#980} Platform: 10895.78.0 (Official Build) stable-channel veyron_minnie This problem is ChromeOS specific. HTML5 Geolocation works correctly on: - Chrome Version 70.0.3538.77 (Official Build) (64-bit) (Win10) - Firefox version 63 (Win10) - Opera version Version:56.0.3051.52 (Win10) Chromebook does not updates HTML5 Geolocation when lid is closed and chromebook is moved to the new location and then wakes up on a new location. It still return coordinates of the previous location. Location coordinates gets updated to new location when user log-out from the Chromebook and re-login. How to reproduce problem on Chromebook: ========================================= 1. Visit page and check location by pressing "Try it" https://www.w3schools.com/html/tryit.asp?filename=tryhtml5_geolocation 2. Close lid on the Chromebook. Do not log-out from the Chromebook! 3. Move to the new location. we moved to the new location that was a few kilometers away. 4. On new location open the lid to wake up Chromebook. 5. Visit HTML5 Geolocation page to check if new location is reported https://www.w3schools.com/html/tryit.asp?filename=tryhtml5_geolocation 6. Wait for more then 10 minutes and try again We did wait for couple of hours but Geolocation there was no Geo-location update Expected Result: ================ Chromebook should update location coordinates when it wakes up on new location. It should not return cached coordinates for the previous location. Actual Result: ============== Chromebook returns Geolocation coordinates for previous location. How frequently does this problem reproduce? ============================================ Always What is the impact to the user, and is there a workaround? If so, what is it? ============================================================================== User needs to logout and re-login to the Chromebook.
,
Oct 31
Thanks for reporting! "We did wait for couple of hours but Geolocation there was no Geo-location update" Does this mean you got the same (cached) result as before, or does it mean the location request never completed/timed out?
,
Oct 31
>>Does this mean you got the same (cached) result as before, or does it mean the location request never completed/timed out? The same, cached result were reported. There was no problem with the timeout or not completed request.
,
Nov 1
The network geolocation request uses your IP address and the set of MAC addresses seen by your WLAN adapter. If the network geolocation provider gets the same set of MAC addresses that it's seen before, then it will return a cached estimate instead of requesting a new estimate. Is it possible that it's seeing some of the same MAC addresses? Are there any wifi APs that traveled with the Chromebook when you changed locations? It's possible that we simply avoided requesting a new location because Chrome thought the device hadn't moved. > The same, cached result were reported. (Assuming we aren't seeing the same MAC addresses), this does sound like a bug. We shouldn't use cached data older than 10 minutes unless the set of nearby MAC addresses are a near match. We are considering a change to the way network location provider works that may address this issue. Whenever we detect a network change, we should clear all cached location data to force the device to acquire a new estimate. This is because network location provider partially determines your location from the request IP address, which is likely to have changed. With this behavior, it would have cleared the cached data after waking and detecting a network change.
,
Nov 1
>>Is it possible that it's seeing some of the same MAC addresses? >>Are there any wifi APs that traveled with the Chromebook when you changed locations? Different WiFi routers were used on each location. So, not possible to get the same MAC addresses reported on each location. Except Chromebook WiFI adapter MAC was the same, since the same Chromebook was used. As mentioned in the initial bug report description, HTML5 Geolocation was reported correctly on the same locations if: - Chrome/FF on Win10 was used - user logout and re-login to the Chromebook.
,
Dec 7
Can we get an update what planes you might have with this issue? Is this going to be fixed and do you have any ETA? FYI, many school use geolocation to determine if student is in or out of school. Student gets then according to the location applied corresponding web filters.
,
Dec 11
toggling emulate geolocation co-ordinates on Windows also has problems with caching https://bugs.chromium.org/p/chromium/issues/detail?id=542923#c1 |
||
►
Sign in to add a comment |
||
Comment 1 by dtapu...@chromium.org
, Oct 29