diff options
| author | mlerman <mlerman@chromium.org> | 2015-05-25 04:40:15 -0700 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-05-25 11:40:49 +0000 |
| commit | 7831f57d5f56e9cafe77388b20a83a90d6eb7918 (patch) | |
| tree | ae659bc4ee503610bf67d6abd532f934bf57b9d5 /components/nacl_helper_nonsfi_unittests.isolate | |
| parent | 870dbbf58c38208eeab114d1c36700aa0460d03c (diff) | |
| download | chromium_src-7831f57d5f56e9cafe77388b20a83a90d6eb7918.zip chromium_src-7831f57d5f56e9cafe77388b20a83a90d6eb7918.tar.gz chromium_src-7831f57d5f56e9cafe77388b20a83a90d6eb7918.tar.bz2 | |
Fix the System Profile to not load extensions. It could otherwise be forced to by GPO.
A few releases ago I introduced a System Profile to back the User Manager (https://codereview.chromium.org/847733005). This profile, however, is causing some problems. I'm trying to reduce those by making clearer the contract of what it's for: A profile that doesn't take a browser window, has no extensions, writes little to disk, etc.
This certainly addresses issue #4 raised within the bug, and address the other issues as well (I can't repro them). This CL generally hardens Chrome for the System Profile in a lot of the same ways we do the Guest Profile.
BUG=482176
TBR=jcivelli@chromium.org (a function, called from chrome/test that lives in c/b/profiles, was renamed).
Review URL: https://codereview.chromium.org/1129293002
Cr-Commit-Position: refs/heads/master@{#331276}
Diffstat (limited to 'components/nacl_helper_nonsfi_unittests.isolate')
0 files changed, 0 insertions, 0 deletions