New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 672924 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

add ExtensionDisabledlist policy

Reported by pdk...@gmail.com, Dec 9 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36

Steps to reproduce the problem:
1. Add extension to ExtensionInstallForcelist.
2. Temporarily remove extension from the list.
3. Re-add extension.

What is the expected behavior?

What went wrong?
The problem is that in step 2 the extension is uninstalled, and so are its settings. An intermediate solution is to provide a way to force-disable an extension, which keeps its settings.

Did this work before? No 

Chrome version: 53.0.2785.143  Channel: n/a
OS Version: Ubuntu 14.04
Flash Version:
 

Comment 1 by emaxx@chromium.org, Dec 10 2016

Cc: devlin@chromium.org asargent@chromium.org
Components: Platform>Extensions
Owner: dskaram@chromium.org
Status: Assigned (was: Unconfirmed)
Assigning to PM for prioritization.

Also CC'ing Extensions folks.
Cc: blumberg@chromium.org
Status: WontFix (was: Assigned)
This will significantly complicate the code and only addresses a very niche use case. Marking as Won'tFix. Adding blumberg@ to make the final call though.
I agree, we have never heard this request before and are not planning to prioritize this request. If you have built an extension that requires complex configuration by the end user, you may want to consider adding a policy for that extension so that it can be restored with a config:

https://www.chromium.org/administrators/configuring-policy-for-extensions

Sign in to add a comment