Issue metadata
Sign in to add a comment
|
Cannot directly edit Location Exceptions
Reported by
epicclan...@gmail.com,
Mar 9 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36 Steps to reproduce the problem: 1. Enter Content Settings -> Location -> Manage Exceptions 2. Cannot enter new exceptions for allow/deny What is the expected behavior? Notification Exceptions directly below has a similar screen that allows the user to manually add notification exceptions. This behavior is expected in the Locations area. What went wrong? Trying to write HTML 5 geolocation code to obtain browser's general location, Chrome denies access. I went to add an exception and discovered that it is impossible. Did this work before? N/A Chrome version: 48.0.2564.116 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 20.0 r0
,
Mar 10 2016
This will be changing with the material redesign but I still don't think it will allow geolocation exceptions to be added. It would be nice to be consistent across permissions. Any thoughts rolfe/finnur?
,
Mar 10 2016
Looks like a feature request, not a security vulnerability.
,
Mar 10 2016
It's not a vulnerability, you can remove exceptions manually, just not add them. As a developer, I would really appreciate the ability to use this line of code without having to actually serve the page:
navigator.geolocation.getCurrentPosition(function(position) { });
I of course do not just want any old .HTML file on my computer to be able to do this as it would be a security concern, so I want to be able to add URL exceptions. Do you not see the benefit here?
,
Mar 10 2016
There's a related bug on this (private right now but finnur@ let me know if you think we can open it up) https://bugs.chromium.org/p/chromium/issues/detail?id=442446#c12 We talked about how only JavaScript has exception options mocked up and implemented but that it wouldn't be a biggie to add it to other settings. I'm OK with it if anyone wants to build it!
,
Jun 15 2016
,
Dec 9 2016
Security>UX component is deprecated in favor of the Team-Security-UX label |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by lgar...@chromium.org
, Mar 10 2016Labels: -Restrict-View-SecurityTeam
Owner: raymes@chromium.org
Status: Assigned (was: Unconfirmed)