Check for equality of the URL's origin in replaceState/pushState

third_party/WebKit/LayoutTests/http/tests/navigation/pushstate-whitelisted-in-blob-denied.html

Index: third_party/WebKit/LayoutTests/http/tests/navigation/pushstate-whitelisted-in-blob-denied.html
diff --git a/third_party/WebKit/LayoutTests/http/tests/navigation/pushstate-whitelisted-in-blob-denied.html b/third_party/WebKit/LayoutTests/http/tests/navigation/pushstate-whitelisted-in-blob-denied.html
new file mode 100644
index 0000000000000000000000000000000000000000..5c5f5432c7f7a5baf648e759f13d8b4924bebef9
--- /dev/null
+++ b/third_party/WebKit/LayoutTests/http/tests/navigation/pushstate-whitelisted-in-blob-denied.html
@@ -0,0 +1,16 @@
+<script>

[Mike West, 2015/12/08 13:45:19]

Please write new tests with `testharness.js` (and consider upstreaming them to
https://github.com/w3c/web-platform-tests/tree/master/html/browsers/history/t...
if the tests there aren't sufficient).

[robwu, 2015/12/08 14:06:39]

All -whitelisted- tests that I introduced here interface closely with Blink's
implementation, and assert that Chromium/Blink behaves properly even with
specific whitelists (that's why I'm using testRunner). Is the current test fine,
or do I still need to change to testharness.js?

[Mike West, 2015/12/08 14:18:41]

`testharness.js` tests have the lovely property of not requiring `-expected.txt`
files. Even if that was the only difference, I think it would still be worth
migrating to that system. :)

+if (window.testRunner) {
+    testRunner.dumpAsText();
+    testRunner.addOriginAccessWhitelistEntry(location.origin, location.protocol, '', false);
+    testRunner.addOriginAccessWhitelistEntry(location.origin, 'blob', '', false);
+}
+
+var blobUrl = URL.createObjectURL(new Blob());
+
+try {
+    history.pushState(null, null, blobUrl);
+    document.write("FAIL: pushState to blob:-URL succeeded.");
+} catch(e) {
+    document.write("PASS: pushState to blob:-URL was blocked.");
+}
+</script>