QuotaTracker: Use 'raw' string as key for origin

QuotaTracker: Use 'raw' string as key for origin

Prior to r382660 the QuotaTracker API took 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() which matches the old behavior without special cases.

BUG=604811
R=michaeln@chromium.org

Committed: https://crrev.com/976f8fa83bf90a5983af3ca8a6e74d34044b93ff
Cr-Commit-Position: refs/heads/master@{#389607}

[jsbell, 2016-04-22 22:14:14]

michaeln@ - please take a look?

[michaeln, 2016-04-25 20:18:30]

lgtm!!

[jsbell, 2016-04-25 20:49:39]

The CQ bit was checked by jsbell@chromium.org

[commit-bot: I haz the power, 2016-04-25 20:50:10]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1914763002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1914763002/20001

[commit-bot: I haz the power, 2016-04-25 23:29:03]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-04-25 23:32:04]

Description was changed from

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

Prior to r382660 the QuotaTracker API took 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() which matches the old behavior without special cases.

BUG=604811
R=michaeln@chromium.org
==========

to

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

Prior to r382660 the QuotaTracker API took 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() which matches the old behavior without special cases.

BUG=604811
R=michaeln@chromium.org

Committed: https://crrev.com/976f8fa83bf90a5983af3ca8a6e74d34044b93ff
Cr-Commit-Position: refs/heads/master@{#389607}
==========

[commit-bot: I haz the power, 2016-04-25 23:32:05]

Patchset 2 (id:??) landed as
https://crrev.com/976f8fa83bf90a5983af3ca8a6e74d34044b93ff
Cr-Commit-Position: refs/heads/master@{#389607}