Comment #1 on issue 72445 by fin...@chromium.org: ExtensionInstallBlacklist
should behave like the global blacklist and disable already installed
extensions
http://code.google.com/p/chromium/issues/detail?id=72445
This feature request did sound familiar when we were discussing it
yesterday and its because I already implemented this a while back,
including a test that is currently enabled and working
(ExtensionServiceTest.BlacklistedByPolicyRemovedIfRunning).
Just to make sure, I tried manually adding the policy in the registry on my
W7 box:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Policies\Google\Chrome\ExtensionInstallBlacklist
REGSZ "1" = "<extensionid>"
And on next startup the extension was gone (I don't know of an easy way to
trigger the PREF_CHANGED while Chrome is running, so I used a restart to
see if it worked but I think it should work while Chrome is running if we
just set the policy the usual way, and not by hand like I did).
I have submitted a CL to make this clearer in the documentation (that a
blacklisted extension gets removed if installed before being blacklisted).