in Group Policy Content Settings value is left behind after turn value to Not configured |
|||
Issue descriptionChrome Version: 62.0.3202.0 OS: Win when switch GP setting from Enable to Not Configured, we expect the Enabled value is deleted, the default setting is restored. But in reality, the Enabled value (e.g cookie, flash, image, js etc) is left behind in with Chrome://settings until user manually reset all settings. What steps will reproduce the problem? (1) in GP Management Editor, set Classic Adminstrative Templates(ADM)-->Google-> Google Chrome->Content Settings->Default cookie setting to Enabled, then select value "Do not allow any site to set local data" (2) gpupdate /force to make this setting in effect, launch Chrome, in Chrome://settings/content/, notice cookie is Blocked. This is expected because this value controlled by GP now. (3) in GP, switch "Default cookies setting" from Enabled to Not Configured (4) after gpupdate /force, launch Chrome, in Chrome://settings/content/, notice cookie is still Blocked instead of default value What is the expected result? when Default cookies setting is set to value "Not Configure", chrome://settings/content/cookies should be reset to default settings. What happens instead? chrome://settings/content/ cookies value is still blocked. This issue also happen to Images, Javascript and Flash setting. After set GP setting to "Not configured", the default setting is NOT restored.
,
Oct 25 2017
Unable to reproduce the issue Windows 10 with chrome #62.0.3202.62, followed the steps mentioned in the comment #0 with cookies, images, javascript Observed policies are working as expected. yiningc@ Could you please help us with screen-cast of this issue Thank You...
,
Oct 25 2017
yiningc@ Is your policy change gets reflected in chrome://policy after force update?
,
Oct 26 2017
I figured out what caused this issue. I used chrome-unsigned/.../policy-template.zip which seems incompatible with released chrome. After start a new environment, use chrome-signed/.../GoogleChromeEnterpriseBundle.zip, this bug not repro anymore. I resolved it as Won't Fix. |
|||
►
Sign in to add a comment |
|||
Comment 1 by yini...@chromium.org
, Oct 24 2017