GeoLocation emulation timestamp does not honor PositionOptions.maximumAge
Reported by
subsoni...@gmail.com,
Jul 25 2017
|
|||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Steps to reproduce the problem: 1. Check out the fiddle at https://jsfiddle.net/krr4vuzL/ and allow your GeoLocation to be read 2. In DevTools, open Menu > More Tools > Sensors 3. In the GeoLocation section, select any pre-defined (or custom) location from the drop-down menu. 4. Refresh the page What is the expected behavior? The printed timestamp should not be the same when refreshing the page, especially since a `PositionOptions.maximumAge` of `0` forbids to use cached values altogether. Instead, this value should be re-computed on every page refresh. What went wrong? The GeoLocation timestamp does not change across page refreshes, even when explicitly disabling cached values Did this work before? No Chrome version: 59.0.3071.115 Channel: stable OS Version: 4.11.9-1-ARCH Flash Version:
,
Jul 26 2017
Tested on Chrome Stable #60.0.3112.78 on Ubuntu 14.04 and able to reproduce the issue. Issue is also reproduced on Windows 7 and Mac 10.12.5 on Chrome stable #60.0.3112.78 and Canary #62.0.3166.0 & 62.0.3167.0 respectively. This is a non-regression issue and able to reproduce from M-54 #54.0.2812.0. Marking it as untriaged so that issue gets addressed. Note: 1. In the builds earlier to 54.0.2812.0, location is not displayed. 2. In the builds earlier to 50.0.2624.0, Sensors option is not found. Thanks.
,
Jul 27 2017
,
Jul 27 2017
Thanks for the report, I can reproduce. The spec seems to agree with you, "If maximumAge is set to 0, the implementation must immediately attempt to acquire a new position object." Is someone on the Location team aware of this? If not, I will take a look.
,
Jul 27 2017
Just to avoid confusion: I made a typo in the title and report. As has already been pointed out, this issue is about `PositionOptions.maximumAge` not being honored. It has nothing to do with `PositionOptions.timeout`. Could someone edit the title?
,
Jul 27 2017
,
Jul 27 2017
Thanks for the clarification! Title+description updated.
,
Sep 22 2017
,
Sep 22 2017
,
Nov 15 2017
,
Nov 16
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by ligim...@chromium.org
, Jul 25 2017