Issue metadata
Sign in to add a comment
|
Geolocation denied based on repeated dismissals
Reported by
msitarze...@gmail.com,
Feb 5 2018
|
||||||||||||||||||||||||
Issue description
Chrome Version : 63.0.3239.132
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari:
Firefox:
Edge:
What steps will reproduce the problem?
(1) Dismiss location request dialog several times.
(2)
(3)
What is the expected result?
See location request again.
What happens instead?
The browser decided for me (not ideal) that the location request was a nuisance.
Please provide any additional information below. Attach a screenshot if
possible.
I'm developing an app that uses geolocation, and need to test all possible options several times. Please offer a toggle in preferences that allows a user to disable this "feature." On by default is fine, but I need it off, and there's no obvious way to disable it.
,
Feb 7 2018
Thanks for the report. You can use the Page Info menu accessible by clicking on the lock icon to reset the permission to Ask. That will also reset the temporary block until you reach the number of dismissals required to trigger it again. We've floated ideas for adding controls for this to DevTools, but haven't had resources to to follow up. Using Page Info to reset is also sufficiently accessible that an additional control hasn't been deemed a must have yet.
,
Feb 7 2018
Thank you! A pointer to this answer in the url presented with the notice will suffice. An alert to the end user would be good at some point. Doing things that are permanent without notifying the user feels deceptive. Great to meet you all. :) Michael Sitarzewski: 303-219-1759 | Personal | inboundgeo | Epic Mini Life
,
Feb 15 2018
msitarzewski@ Thanks for the issue. As per comment #3, can you please confirm the closure of this issue, as the information given in comment #2 has helped you with this issue. Thanks..
,
Feb 15 2018
Yes, this can be closed. A new feature request should be added to document this answer in the “more information “ url provided in the console. Thank you. Michael Sitarzewski: 303-219-1759 | Personal | inboundgeo | Epic Mini Life
,
Feb 15 2018
Thank you for providing more feedback. Adding requester "susan.boorgula@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 22 2018
CL at crrev.com/c/930608.
,
Feb 22 2018
,
Feb 26 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0b679185592fd608a2a5e422b3e89362e6f518fe commit 0b679185592fd608a2a5e422b3e89362e6f518fe Author: Dominick Ng <dominickn@chromium.org> Date: Mon Feb 26 00:34:08 2018 Clarify in the console message that permissions embargo can be cleared. This is intended to help developers who see the console messages during testing of sites. BUG= 808896 Change-Id: I4353bb6417c8b3b97d307c1f9afd4ad23b447549 Reviewed-on: https://chromium-review.googlesource.com/930608 Reviewed-by: Raymes Khoury <raymes@chromium.org> Commit-Queue: Dominick Ng <dominickn@chromium.org> Cr-Commit-Position: refs/heads/master@{#539054} [modify] https://crrev.com/0b679185592fd608a2a5e422b3e89362e6f518fe/chrome/browser/permissions/permission_context_base.cc
,
Feb 26 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Feb 6 2018