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

third_party/WebKit/LayoutTests/http/tests/navigation/pushstate-at-unique-origin-denied.html

Index: third_party/WebKit/LayoutTests/http/tests/navigation/pushstate-at-unique-origin-denied.html
diff --git a/third_party/WebKit/LayoutTests/http/tests/navigation/pushstate-at-unique-origin-denied.html b/third_party/WebKit/LayoutTests/http/tests/navigation/pushstate-at-unique-origin-denied.html
new file mode 100644
index 0000000000000000000000000000000000000000..a775c71d7e45d030b5c8aab97d3850fb0407d55c
--- /dev/null
+++ b/third_party/WebKit/LayoutTests/http/tests/navigation/pushstate-at-unique-origin-denied.html
@@ -0,0 +1,12 @@
+<meta http-equiv="Content-Security-Policy" content="sandbox allow-scripts">
+<script>

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

Please write new tests with `testharness.js` (and consider upstreaming the
non-Chrome-specific bits 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]

I believe that the test is not suited for the test harness, because the imported
tests run at file:// with universal access. This is also the reason why this
expectation failed:
https://chromium.googlesource.com/chromium/src/+/1eb37c3ac47c16d2b463879a2402...

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

That's a bug in the way that we're running those tests. We ought to be running
them through `wptserve`, but that isn't wired up to the test runner yet. If you
execute the tests from http://w3c-test.org/tools/runner/index.html, you'll see
more reasonable results. There's value to the ecosystem in upstreaming these
tests, even if we're doing a bad job as a project at running them in an
automated fashion.

+if (window.testRunner) {
+    testRunner.dumpAsText();
+}
+try {
+    history.pushState(null, null, document.URL);
+    document.write("FAIL URL at unique origin was manipulated via pushState.");
+} catch(e) {
+    document.write("PASS: unique URLs cannot be manipulated via pushState.");
+}
+</script>