diff options
| author | dconnelly@chromium.org <dconnelly@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-11-21 13:04:28 +0000 |
|---|---|---|
| committer | dconnelly@chromium.org <dconnelly@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-11-21 13:04:28 +0000 |
| commit | f97bd48680e0d3809f521dbcb06bd36aae5eaf0b (patch) | |
| tree | 89c79bce7dacfb0cb601460247c8b748d84b6d6e /chrome/browser/omnibox | |
| parent | cead7ee37b1c9f0597c5033f6593901c14865283 (diff) | |
| download | chromium_src-f97bd48680e0d3809f521dbcb06bd36aae5eaf0b.zip chromium_src-f97bd48680e0d3809f521dbcb06bd36aae5eaf0b.tar.gz chromium_src-f97bd48680e0d3809f521dbcb06bd36aae5eaf0b.tar.bz2 | |
Move ProxyPolicy fixup logic out of PolicyProvider and inject it instead.
The logic was previously applied at the UpdatePolicy level of every
ConfigurationPolicyProvider, but this needs to move to facilitiate the
refactoring of chrome/browser/policy into a layered component. Instead
a fixup function can be injected into a PolicyService at construction
time and is applied before policies from the various PolicyProviders
are merged.
There are three tests for this:
- PolicyTransformationsTest.FixDeprecatedPolicies tests that the proxy
policy fixup function works properly.
- PolicyServiceTest.PolicyPreprocessing tests that the preprocessor
function is applied during policy merge.
- PolicyTest.PolicyPreprocessing tests that the proxy fixup function
is added BrowserPolicyConnector and ProfilePolicyConnector.
TEST=unit test, integration test, browser test
BUG=271392
Review URL: https://codereview.chromium.org/59243005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@236511 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/omnibox')
0 files changed, 0 insertions, 0 deletions