1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
|
<!DOCTYPE html>
<meta charset="utf-8">
<title>Navigating forward after replace() should still trigger hashchange</title>
<link rel="help" href="https://html.spec.whatwg.org/multipage/#history-traversal">
<link rel="author" href="mailto:d@domenic.me" title="Domenic Denicola">
<!-- While writing ./replacement-enabled.html, a bug was discovered in Firefox where it does not
fire hashchange when using history.forward(), at least under certain conditions. So, this test
exercises that specifically. -->
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<script src="navigate-helpers.js"></script>
<body>
<script>
"use strict";
let resolve, iframe;
promise_test(() => {
iframe = document.createElement("iframe");
iframe.src = "/common/blank.html";
iframe.addEventListener("load", runTest);
document.body.appendChild(iframe);
return new Promise(r => resolve = r);
});
function runTest() {
iframe.removeEventListener("load", runTest);
const frameWindow = iframe.contentWindow;
resolve((async () => {
await navigateAndWaitForChange(frameWindow, w => w.location.href = "/common/blank.html#apple");
await navigateAndWaitForChange(frameWindow, w => w.location.href = "/common/blank.html#banana");
await navigateAndWaitForChange(frameWindow, w => w.location.href = "/common/blank.html#cat");
await navigateAndWaitForChange(frameWindow, w => w.history.back());
await navigateAndWaitForChange(frameWindow,
w => w.location.replace("/common/blank.html#zebra"));
await navigateAndWaitForChange(frameWindow, w => w.history.forward());
})());
}
</script>
|
