Issue metadata
Sign in to add a comment
|
Content settings can have strikethrough "Allow" enterprise policy entries. |
||||||||||||||||||||||||
Issue descriptionChrome 53.0.2783.5 OSX 10.11.5 What steps will reproduce the problem? (1) Open the Chrome profile of a Googler (2) Visit chrome://settings/contentExceptions#plugins What is the expected output? Stuff that makes sense. What do you see instead? Policy exceptions set to "Allow", but with a strikethrough. The "Learn more" link is useless. Does anyone know what these are? Should we have a better explanation? Will the new Material content settings fix this?
,
Aug 25 2016
Related: https://crbug.com/628733
,
Sep 14 2016
huangs@ explicitly added this feature. huangs@ - could you explain what this means?
,
Nov 22 2016
,
Dec 13 2016
We should improve the UI around exceptions.
,
Dec 13 2016
,
Dec 14 2016
The UI may be improved already in the new version of site settings, but I haven't checked yet.
,
Nov 10 2017
,
Nov 16 2017
Closing as WontFix due to the change to Material Settings (which doesn't seem to have strikethroughs for anything). :) |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by lgar...@chromium.org
, Jul 8 2016