Force databases and localstorage to be enabled extensions.

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
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=24841

[Erik does not do reviews, 2009-08-24 23:25:26]

LGTM

http://codereview.chromium.org/173306/diff/1014/1015
File chrome/browser/extensions/extension_storage_apitest.cc (right):

http://codereview.chromium.org/173306/diff/1014/1015#newcode8
Line 8: ASSERT_TRUE(RunExtensionTest("storage")) << message_;
yay!

http://codereview.chromium.org/173306/diff/1014/1025
File webkit/glue/webpreferences.cc (right):

http://codereview.chromium.org/173306/diff/1014/1025#newcode51
Line 51: settings->setDatabasesEnabled(WebKit::databasesEnabled() ||
databases_enabled);
80 cols

[dumi, 2009-08-25 00:07:44]

lgtm

[jorlow, 2009-08-25 17:25:15]

LGTM

On Mon, Aug 24, 2009 at 5:07 PM, <dumi@chromium.org> wrote:

> lgtm
>
>
> http://codereview.chromium.org/173306
>