Site details shows lots of empty permissions |
|||||
Issue descriptionChrome 63.0.3218.0 macOS 10.12.6 What steps will reproduce the problem? (1) Change some permissions. (2) Visit chrome://settings/content/siteDetails?site=https%3A%2F%2Fpermission.site What is the expected result? I see values for all the permissions. What happens instead? All permissions from "Flash" onward are blank (see screenshots). Since the site last had no non-default permissions, I have only changed permissions using Page Info and Site details, in this particular Chrome version. patricialor@: Is there a good place I can start to debug this for you?
,
Oct 10 2017
Looks like this happens if you set Flash to "Ask". I presume this is related to Issue 697238 .
,
Oct 10 2017
The console will probably have a failed assert logged :( Thanks for finding this!
,
Oct 17 2017
Chrome 63.0.3223.8
macOS 10.12.6
crisper.js:20 Uncaught (in promise) Error: Assertion failed: Only extensions or enterprise policy can change the setting to ASK.
at assert (crisper.js:20)
at HTMLElement.isNonDefaultAsk_ (lazy_load.crisper.js:180)
at HTMLElement._annotatedComputationEffect (polymer-extracted.js:1623)
at HTMLElement._effectEffects (polymer-extracted.js:1432)
at HTMLElement._propertySetter (polymer-extracted.js:1416)
at HTMLElement.setter (polymer-extracted.js:1495)
at exceptionList.forEach (lazy_load.crisper.js:188)
at Array.forEach (<anonymous>)
at browserProxy.getOriginPermissions.then.exceptionList (lazy_load.crisper.js:188)
at <anonymous>
This is in my Chromium profile, not my google.com profile, which I think means there should not be an enterprise policy from the organization.
(But it may be applied from the filesystem-specific defaults on macOS?)
,
Oct 23 2017
It's weird that you have "Ask" as an option in the drop down for Flash. Mine looks different - I have Ask (Default) Allow Block (That's on Canary at least). Did something change between 63 and 64?
,
Nov 10 2017
,
Feb 18 2018
,
Oct 27
,
Oct 29
Cannot reproduce in M-70 (with google.com profile) nor trunk, and there's no longer a failed assertion logged. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by lgar...@chromium.org
, Oct 10 2017