diff options
| author | felt@chromium.org <felt@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-09 13:08:33 +0000 |
|---|---|---|
| committer | felt@chromium.org <felt@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-09 13:08:33 +0000 |
| commit | 770d6a89638d340c3bad7970614923dc17e54d8c (patch) | |
| tree | 4710e00082876cc07f0ae569b067c24a4debb1be /chrome/browser/extensions/extension_prefs_scope.h | |
| parent | 93bea07805f39bed67286e705852e66de8c122a4 (diff) | |
| download | chromium_src-770d6a89638d340c3bad7970614923dc17e54d8c.zip chromium_src-770d6a89638d340c3bad7970614923dc17e54d8c.tar.gz chromium_src-770d6a89638d340c3bad7970614923dc17e54d8c.tar.bz2 | |
Change when Activity Log is enabled
Previously, the ActivityLog was only enabled when a flag was set. Now it will be enabled when the flag is set OR if someone has installed an extension that uses the activityLogPrivate API.
There are now two ways to check the Activity Log state:
1. Call the non-static ActivityLog::IsLogEnabled method, which will give a guaranteed correct answer for the current profile.
2. Call the static ActivityLog::IsLogEnabledOnAnyProfile method, which will tell you if the extension is installed on any profile at all. This is only meant to be used when it would be hard to get a profile object.
BUG=241672
R=mpcomplete@chromium.org
Review URL: https://chromiumcodereview.appspot.com/16608002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@205120 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/extensions/extension_prefs_scope.h')
0 files changed, 0 insertions, 0 deletions