Issue metadata
Sign in to add a comment
|
Website not calling the GPS for new position
Reported by
andrewco...@gmail.com,
Dec 6 2017
|
||||||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: 1. Use an older version of Chrome (eg 43) and use the get current position function. Watch the webpage trigger the GPS and get a current position 2. Use the current version of chrome to do the same, and note that while the GPS status bar icon flashes very quickly, no new position is returned. 3. What is the expected behavior? That the GPS is asked for, and returns, a new position (triggering the flashing "location services" icon in the status bar). What went wrong? We have a website with an option to get the GPS position from the device (Samsung G Tab SM-T535). In earlier Chrome (I just reverted to Chrome 43 to test), when the "get current position" was selected, the GPS status bar icon would flash for say 10 seconds and a new position would be returned. Somewhere in the last few chrome versions the behavior has changed. Now when the "get current position" button is selected, the GPS status bar icon flashes very quickly, but no new position is returned. Nothing else has changed in the configuration of the webpage or on the tablet. We have 30+ tablets and are seeing the same issue across the board. Sorry I'm not a developer but can provide more information if i'm told what to provide. Did this work before? Yes Approx 43 (whatever the android version was when the SM-T535 was released, and many versions since. Chrome version: 62.0.3202.84 Channel: stable OS Version: 5.0.2 Flash Version: Unknown Happy to provide any additional info if I'm told what to provide.
,
Dec 13 2017
I believe at some point we changed Chrome so that GPS data is provided only to secure web sites (https ones), as GPS can be sensitive information. Is your web page secure? (If it's not, Chrome will block the request. That said, if the request is blocked, it shouldn't cause a flash in the omnibox. If it does, that's a bug.)
,
Dec 13 2017
We've implemented a number of security improvements which could account for the blocked geolocation. Chrome 43 is very old. Could you provide specific steps to reproduce the problem, including the website that you're seeing the issue on?
,
Dec 13 2017
,
Dec 18 2017
andrewcox83@gmail.com, could you provide more specific repro steps?
,
Dec 18 2017
Closing as WontFix as we haven't heard from the OP for over a week.
,
Dec 21 2017
The NextAction date has arrived: 2017-12-21 |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by msrchandra@chromium.org
, Dec 6 2017Labels: Needs-triage-Mobile Needs-Feedback