Move IndexedDBKey, IndexedDBKeyRange into content namespace

Move IndexedDBKey, IndexedDBKeyRange into content namespace

R=jam@chromium.org
BUG=125589
TEST=none


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=135487

[jsbell, 2012-04-30 21:27:04]

Migrating IDB code to content namespace. Not everything, but two of the more
widely used types.

I eschewed "using" aliases in most places since content::SerializedScriptValue
(for example) was used with a fully qualified name. I'm happy to go back and add
"using content::IndexedDBxxxxx;" statements if that form is preferred,
especially as some of these classes should be moving into content themselves.
Preferences?

[jam, 2012-05-01 01:54:14]

lgtm, thanks

as you guessed, we do favor "using content::" in cc files inside content, since
eventually all that code needs to move to the content namespace

[jsbell, 2012-05-03 18:40:02]

On 2012/05/01 01:54:14, John Abd-El-Malek wrote:
> as you guessed, we do favor "using content::" in cc files inside content,
since
> eventually all that code needs to move to the content namespace

jam@ can you take a look at the updated patch, to confirm this matches the
desired style?

[commit-bot: I haz the power, 2012-05-04 22:08:02]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/jsbell@chromium.org/10272018/4001

[commit-bot: I haz the power, 2012-05-04 23:37:56]

Change committed as 135487