diff options
| author | aa@chromium.org <aa@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-08-25 08:23:00 +0000 |
|---|---|---|
| committer | aa@chromium.org <aa@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-08-25 08:23:00 +0000 |
| commit | a6ec2b5503d4914c03eb4439ba3ab3958eeccb9b (patch) | |
| tree | 67b45325fb88f217a16c56619ffc947f086204ea /net | |
| parent | 077b4b68fc278a0d81e4f7e1582d2144f4ccf9d5 (diff) | |
| download | chromium_src-a6ec2b5503d4914c03eb4439ba3ab3958eeccb9b.zip chromium_src-a6ec2b5503d4914c03eb4439ba3ab3958eeccb9b.tar.gz chromium_src-a6ec2b5503d4914c03eb4439ba3ab3958eeccb9b.tar.bz2 | |
Force databases and localstorage to be enabled extensions.
We were already doing this, this change modifies the
mechanism. Before we were relying on the presence of the
--enable-extensions flag, but as we are getting ready to
remove that on dev, we needed something else.
This forces local storage and database to be enabled on
chrome-extension:// pages.
Also, change the way database enabling works in general to
be more like the way local storage works, just for
consistency. Will remove old, unnecessary WebKit API in an
upstream change.
erikkay: extensions stuff
dumi: database stuff
jorlow: local storage stuff
BUG=19511
Review URL: http://codereview.chromium.org/173306
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@24223 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions