-
Notifications
You must be signed in to change notification settings - Fork 411
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ExtensionSettings and removing add-ons #1124
Comments
That actually sounds like a bug (that they aren't uninstalled) Chrome introduced "removed" to explicitly remove things https://support.google.com/chrome/a/answer/9867568?hl=en Do you want them disabled or removed? |
It seems right to me: delete if I specified "blocked" and do nothing if I specified nothing. Otherwise "blocked" is identical to "not specified" |
The tricky part is making this change without impacting the old behavior. I wonder if I need to add a version flag to this JSON? I'm going to look at Chrome to see exactly what they do. |
I think the best thing to do is this:
|
If I specify the following in Extension settings:
all installed extensions (except those listed in "installation_mode": "allowed") will be removed. This is correct.
but if I specify something like this:
all installed add-ons (except those listed in "installation_mode": "allowed", and any languages and dictionaries ) will be blocked (grayed out), but not removed. This is not obvious, because if I wanted to remove or block installed extensions (for the user it is the same thing), I would use "blocked".
Is it possible to specify what to do with extensions that are not explicitly described as "blocked" in the policy: "gray out" or "do nothing"?
The text was updated successfully, but these errors were encountered: