Chrome run with --headless and --enable-geolocation gives "User denied Geolocation"
Reported by
icart...@thoughtworks.com,
Apr 19 2018
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36 Steps to reproduce the problem: 1. run chrome with --headless and --enable-geolocation 2. Call geolocation.getCurrentPosition(...) from javascript within a page 3. Returns positionError object with message="User denied Geolocation" What is the expected behavior? Return a valid position, works fine without "--headless" option (and on firefox headless) What went wrong? Javascript method getCurrentPosition() Returns positionError object with message="User denied Geolocation" Did this work before? No Chrome version: 66.0.3359.117 Channel: stable OS Version: OS X 10.13.3 Flash Version: Being run via webdriver 3.11.0 and chromedriver 2.38
,
Apr 20 2018
This issue seems to be out of scope as this is related to headless and chromedriver. Hence adding TE-NeedsTriageHelp label. Could someone from dev team please have a look at the issue. Thanks!
,
Apr 20 2018
,
Oct 27
I'm looking for a way to use geolocation in headless mode. However, where did you get the --enable-geolocation argument? I can't see it in the list of the supported arguments: https://peter.sh/experiments/chromium-command-line-switches/ PS: Now, I'm using "non-headless" mode and --disable-search-geolocation-disclosure to test geolocation. |
|||
►
Sign in to add a comment |
|||
Comment 1 by vamshi.kommuri@chromium.org
, Apr 19 2018Labels: Needs-Triage-M66