DatabaseTracker: Use 'raw' string as key for origin

DatabaseTracker: Use 'raw' string as key for origin

Prior to r382660 the WebSQL implementation used DatabaseIdentifiers, and
a serialization was used as the key in maps. This was changed to take
SecurityOrigins instead and the serialization via toString(). This
introduced additional special cases e.g. "null" for file:// origins in
some cases, leading to mismatches between setting and lookup in the
map depending on when the SecurityOrigin was minted. To fix, use
toRawString() within the DatabaseTracker which matches the old behavior.

Similarly, use toRawString() when serializing an origin for posting
across threads.

BUG=618381
R=michaeln@chromium.org

Review-Url: https://codereview.chromium.org/2050803005
Cr-Commit-Position: refs/heads/master@{#399743}
(cherry picked from commit 1667e9b86e2ede1e6267db73445478b447cca2e8)

Committed: https://chromium.googlesource.com/chromium/src/+/09a5bbb16c83ffad3ec63a6e272367428c190a2a

[michaeln, 2016-06-17 22:11:19]

Description was changed from

==========
DatabaseTracker: Use 'raw' string as key for origin

Prior to r382660 the WebSQL implementation used DatabaseIdentifiers, and
a serialization was used as the key in maps. This was changed to take
SecurityOrigins instead and the serialization via toString(). This
introduced additional special cases e.g. "null" for file:// origins in
some cases, leading to mismatches between setting and lookup in the
map depending on when the SecurityOrigin was minted. To fix, use
toRawString() within the DatabaseTracker which matches the old behavior.

Similarly, use toRawString() when serializing an origin for posting
across threads.

BUG=618381
R=michaeln@chromium.org

Review-Url: https://codereview.chromium.org/2050803005
Cr-Commit-Position: refs/heads/master@{#399743}
(cherry picked from commit 1667e9b86e2ede1e6267db73445478b447cca2e8)
==========

to

==========
DatabaseTracker: Use 'raw' string as key for origin

Prior to r382660 the WebSQL implementation used DatabaseIdentifiers, and
a serialization was used as the key in maps. This was changed to take
SecurityOrigins instead and the serialization via toString(). This
introduced additional special cases e.g. "null" for file:// origins in
some cases, leading to mismatches between setting and lookup in the
map depending on when the SecurityOrigin was minted. To fix, use
toRawString() within the DatabaseTracker which matches the old behavior.

Similarly, use toRawString() when serializing an origin for posting
across threads.

BUG=618381
R=michaeln@chromium.org

Review-Url: https://codereview.chromium.org/2050803005
Cr-Commit-Position: refs/heads/master@{#399743}
(cherry picked from commit 1667e9b86e2ede1e6267db73445478b447cca2e8)

Committed:
https://chromium.googlesource.com/chromium/src/+/09a5bbb16c83ffad3ec63a6e2723...
==========

[michaeln, 2016-06-17 22:11:21]

Committed patchset #1 (id:1) manually as
09a5bbb16c83ffad3ec63a6e272367428c190a2a.