commit | e8634172cb47984f8432daf97f62bd578311d8f1 | [log] [tgz] |
---|---|---|
author | lazyboy <[email protected]> | Thu Jan 28 00:10:48 2016 |
committer | Commit bot <[email protected]> | Thu Jan 28 00:11:41 2016 |
tree | c57b1603289968647258a7db442cea16e35d5ce1 | |
parent | 12556951e56fb712f8fab1ec24eb73447a448f19 [diff] |
Observe adding external extensions via windows registry. Install the extension right away (no chrome restart). For registry changes, we only look at 32-bit registry values for extensions, see https://developer.chrome.com/extensions/external_extensions#registry A lot of the changes in this CL is to make ExternalProvider-s be able to discover new external extensions at times other than chrome start up. The added method is OnExternalProviderUpdateComplete(), which provides a list of a. Extensions that were added via update_url, b. Extensions that were added via crx, c. Extensions that were removed. BUG=581756 Test=While chrome is running, add a registry entry for an extension under HKLM or HKCU as described in https://developer.chrome.com/extensions/external_extensions#registry Now observe that external install would appear for that extension in chrome shortly. If you had some extension installed this way, removing the registry entry would cause the extension to be uninstalled too! Review URL: https://codereview.chromium.org/1495403002 Cr-Commit-Position: refs/heads/master@{#371911}