diff options
| author | pam@chromium.org <pam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-06-02 13:14:14 +0000 |
|---|---|---|
| committer | pam@chromium.org <pam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-06-02 13:14:14 +0000 |
| commit | 6518715de7d13fee24c654377a29da2e643b05e5 (patch) | |
| tree | 1e916cbec83cc4dcbc4f8b7dcffc3368f91da3f9 /chrome/browser/extensions/api/web_request | |
| parent | bb5035d4a6048baf8b1f2801114d058134833a40 (diff) | |
| download | chromium_src-6518715de7d13fee24c654377a29da2e643b05e5.zip chromium_src-6518715de7d13fee24c654377a29da2e643b05e5.tar.gz chromium_src-6518715de7d13fee24c654377a29da2e643b05e5.tar.bz2 | |
Refactor the various ways to control what users can do to extensions.
Add an ExtensionManagementPolicy class, held by the ExtensionService, that registers delegates and mediates questions about what can be done to extensions (install, uninstall, modify, etc.). Convert existing mechanisms to control extension operations, namely administrator policy black/whitelists and component extension requirements, to use this abstraction.
In addition to cleaning up existing mechanisms, this will support the control managed mode needs to impose (in an upcoming patch).
BUG=117987
TEST=covered by unit, browser, and api tests
Review URL: https://chromiumcodereview.appspot.com/10382149
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@140194 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/extensions/api/web_request')
0 files changed, 0 insertions, 0 deletions