Issue metadata
Sign in to add a comment
|
Expose `Coordinates.accuracy` in GeoLocation emulation
Reported by
subsoni...@gmail.com,
Jun 28 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. In DevTools, open More Tools > Sensors 2. Observe that "Latitude" and "Longitude" are the only inputs 3. Note that there is no "Accuracy" input, although the API should report a corresponding `accuracy` value for every coordinate What is the expected behavior? There should be an input labeled "Accuracy" that sets `Coordinates.accuracy` (compare https://developer.mozilla.org/en-US/docs/Web/API/Coordinates/accuracy) What went wrong? The current `accuracy` is implicitly assumed to be a constant `150`. Did this work before? No Chrome version: 59.0.3071.115 Channel: beta OS Version: 4.11.6-3-ARCH Flash Version:
,
Jun 29 2017
This issue seems more like a Feature request, hence untriaging so that it get's addressed. Thanks!!
,
Jul 5 2017
,
Nov 15 2017
Thanks for the report. Sorry for the late response. There's a duplicate bug to add all the extra supported properties: altitude altitudeAccuracy heading speed |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by nyerramilli@chromium.org
, Jun 29 2017