Issue 769231 in chromium: navigator.geolocation.getCurrentPosition ignores maximumAge

[mattreyn… via monorail]

Comment #8 on issue 769231 by mattre...@chromium.org: navigator.geolocation.getCurrentPosition ignores maximumAge
https://bugs.chromium.org/p/chromium/issues/detail?id=769231#c8

I tested the behavior of other browsers to help us determine how fixing this bug will affect existing web content.

Firefox 56:

maximumAge is handled correctly. Firefox will prefer to return a cached estimate when available, as long as the age of the estimate is less than maximumAge. When maximumAge is zero, returned estimates are always newer than the call to getCurrentPosition. Firefox appears to do some rate limiting; when maximumAge is zero (indicating we want a fresh estimate) the callbacks from subsequent calls can be delayed by as much as five seconds.

Edge 38.14393.1066.0:

Edge does not handle maximumAge correctly. It's possible Edge never caches position estimates and always returns new estimates. Setting maximumAge:Infinity, timeout:0 (indicating we want a cached estimate of any age) fails with TIMEOUT, even after previous geolocation calls succeed in returning an estimate.

Safari 10.1.2 (12603.3.8):

Safari doesn't recognize "Infinity" as a valid timeout value, so I used 1000000 instead. The timestamp returned with the position estimate uses the wrong epoch (Jan 1, 2001 UTC). Correcting for this, it appears that sometimes Safari will return an estimate that is older than maximumAge. This is most common after a long period of inactivity, and does not persist (ie, the next call will usually return a timestamp younger than maximumAge). This occurs even when maximumAge is zero. When a cached estimate is requested (maximumAge:1000000, timeout:0), it always fails with TIMEOUT even if a recent geolocation call succeeded.

Internet Explorer 11.1770.14393.0

A position estimate is only returned on the first call to getCurrentPosition, subsequent calls fail with POSITION_UNAVAILABLE. Timeout:0 is not handled properly and will always fail with TIMEOUT, even when a cached estimate is available.

--
You received this message because:
1. A rule CC'd you on the issue
2. You are auto-CC'd on all issues in component Blink>Geolocation

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.