Correctly construct ("file", "", 0) SecurityOrigins.

Correctly construct ("file", "", 0) SecurityOrigins.

This allows us to round-trip "file://" origins through url::Origin and
WebSecurityOrigin without data loss.

BUG=515797
R=nasko@chromium.org,jochen@chromium.org

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=199843

[Mike West, 2015-07-31 08:09:08]

Jochen, Nasko, mind taking a look?

-mike

[jochen (gone - plz use gerrit), 2015-07-31 08:15:01]

https://codereview.chromium.org/1266963002/diff/1/Source/platform/weborigin/S...
File Source/platform/weborigin/SecurityOriginTest.cpp (right):

https://codereview.chromium.org/1266963002/diff/1/Source/platform/weborigin/S...
Source/platform/weborigin/SecurityOriginTest.cpp:378: {"file", "example.com", 0,
"file://"},
Hm, file: can have a host, no?

[Mike West, 2015-07-31 15:21:27]

https://codereview.chromium.org/1266963002/diff/1/Source/platform/weborigin/S...
File Source/platform/weborigin/SecurityOriginTest.cpp (right):

https://codereview.chromium.org/1266963002/diff/1/Source/platform/weborigin/S...
Source/platform/weborigin/SecurityOriginTest.cpp:378: {"file", "example.com", 0,
"file://"},
On 2015/07/31 at 08:15:01, jochen wrote:
> Hm, file: can have a host, no?

Yup. We serialize every `file:` URL as `file://` at the moment. Changing it to
include the host is probably a good idea, but that's not our current behavior.

[jochen (gone - plz use gerrit), 2015-07-31 15:47:01]

lgtm

[nasko, 2015-07-31 15:54:23]

LGTM

[nasko, 2015-07-31 15:54:35]

The CQ bit was checked by nasko@chromium.org

[commit-bot: I haz the power, 2015-07-31 15:54:46]

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

[commit-bot: I haz the power, 2015-07-31 15:58:36]

Committed patchset #1 (id:1) as
https://src.chromium.org/viewvc/blink?view=rev&revision=199843