diff options
| author | mpcomplete@chromium.org <mpcomplete@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-08-31 18:40:32 +0000 |
|---|---|---|
| committer | mpcomplete@chromium.org <mpcomplete@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-08-31 18:40:32 +0000 |
| commit | bc535ee5bb4eece29f5d88bcc688613b3b208b27 (patch) | |
| tree | 37b90c6bbbe98732c81515b35f02f8b835ac5df7 /chrome/browser/extensions/extension_function.h | |
| parent | 7566dbf757617f9e77f4a7f9f031402eb7818b04 (diff) | |
| download | chromium_src-bc535ee5bb4eece29f5d88bcc688613b3b208b27.zip chromium_src-bc535ee5bb4eece29f5d88bcc688613b3b208b27.tar.gz chromium_src-bc535ee5bb4eece29f5d88bcc688613b3b208b27.tar.bz2 | |
Add support for a "split" incognito behavior for extensions.
- On by default for apps, off by default for extensions.
- Split mode means "run incognito extensions in a separate process if the user
says OK, and the two processes can only see their own profile."
- Spanning mode is what we have now, and means "run a single extension process,
but allow it to access both profiles if the user says OK."
BUG=49232
BUG=49114
TEST=extensions still work in incognito when you check "Allow in Incognito".
Review URL: http://codereview.chromium.org/3210007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@58033 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/extensions/extension_function.h')
| -rw-r--r-- | chrome/browser/extensions/extension_function.h | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/chrome/browser/extensions/extension_function.h b/chrome/browser/extensions/extension_function.h index 51f25fe..b48d0a9 100644 --- a/chrome/browser/extensions/extension_function.h +++ b/chrome/browser/extensions/extension_function.h @@ -149,7 +149,10 @@ class ExtensionFunction : public base::RefCountedThreadSafe<ExtensionFunction> { // of this call. bool has_callback_; - // True if this callback should include information from incognito contexts. + // True if this callback should include information from incognito contexts + // even if our profile_ is non-incognito. Note that in the case of a "split" + // mode extension, this will always be false, and we will limit access to + // data from within the same profile_ (either incognito or not). bool include_incognito_; // True if the call was made in response of user gesture. |