Unable to add exceptions via [hostname pattern] and [behavior] under managing exceptions menu
Reported by
cole.um...@gmail.com,
Feb 2 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Steps to reproduce the problem: 1. Go to chrome://settings/contentExceptions#media-stream What is the expected behavior? The dialog box should show input field to enable adding Hostname pattern and Behavior, so that one can add the address for which to explicitly to enable an exception. What went wrong? There is no input field. Did this work before? Yes Chrome version: 55.0.2883.87 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 24.0 r0 There is a link [https://support.google.com/chrome/answer/3123708?visit_id=0-636216527305280644-1310245820&p=settings_manage_exceptions&rd=1] which is useless as it directs to add hostname pattern and behavior but this function does not exist even though it should as it is useful for flexible management of devices [in this case specifically microphone access]. As a developer, there's always need to test deployments and have ability to make exceptions such as when running under 'localhost' etc. So this needs to be resolved. As an end user, I like to be able to decide which sites I want to allow/disallow certain types of access.
,
Feb 2 2017
msramek@, Can you take a look at this issue? Thanks.
,
Feb 2 2017
,
Feb 6 2017
,
Feb 6 2017
There are several things to address. 1. The link chrome://settings/contentExceptions#media-stream leads to the exception page of the mediastream (combined camera+mic) content setting which was deprecated a long time ago. It's an invalid URL. Nowadays, we have separate camera and mic exceptions: chrome://settings/contentExceptions#media-stream-mic, chrome://settings/contentExceptions#media-stream-camera. 2. The old content settings menu was designed with the idea that sensitive permissions should only be given in context, i.e. through a permission prompt, not in advance. That's why editing was disabled for mediastream (and later mic and camera). The new revamped settings page no longer follows this idea - please try chrome://md-settings . 3. Even without this menu, there should be no problem testing media permissions on localhost. Your website will popup a permission prompt and you can accept it. One thing to note is that media permissions are not sticky in insecure contexts; but localhost is treated as secure by most APIs, so I would expect that isn't a problem here either.
,
Feb 6 2017
Thanks msramek@ for the updated pointer to the revamped settings page chrome://md-settings. That's definitely more flexible and more importantly usable. Is there any plan to make this the default settings menu, in lieu of the current 'old' version? In terms of localhost, popups are subject to things such as 'enterprise policy, so for those cases when popups don't actually 'pop up' then it's vital to be able to manually adjust certain configurations. Thanks for your help! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by xzhou@chromium.org
, Feb 2 2017Labels: -Restrict-View-SecurityTeam allpublic
Status: Untriaged (was: Unconfirmed)