File: navigate-history-back-bfcache.html

package info (click to toggle)
firefox-esr 140.4.0esr-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 4,539,276 kB
  • sloc: cpp: 7,381,286; javascript: 6,388,710; ansic: 3,710,139; python: 1,393,780; xml: 628,165; asm: 426,918; java: 184,004; sh: 65,742; makefile: 19,302; objc: 13,059; perl: 12,912; yacc: 4,583; cs: 3,846; pascal: 3,352; lex: 1,720; ruby: 1,226; exp: 762; php: 436; lisp: 258; awk: 247; sql: 66; sed: 54; csh: 10
file content (24 lines) | stat: -rw-r--r-- 1,024 bytes parent folder | download | duplicates (11) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
 
<!doctype html>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<script src="/common/utils.js"></script>
<script src="/common/dispatcher/dispatcher.js"></script>
<script src="/html/browsers/browsing-the-web/back-forward-cache/resources/helper.sub.js"></script>

<script>
runBfcacheTest({
  targetOrigin: originSameOrigin,
  funcBeforeBackNavigation: () => {
    window.did_navigate = false;
    navigation.onnavigate = () => window.did_navigate = true;
  },
  async funcAfterAssertion(pageA, pageB) {
    // When `funcAfterAssertion` is called, we've already navigated to pageB,
    // then gone back to pageA with bfcache. Now go forward to pageB so we can
    // observe whether the navigate event fired.
    await pageA.execute_script(() => history.forward());
    await pageB.execute_script(waitForPageShow);
    assert_true(await pageB.execute_script(() => window.did_navigate));
  }
}, "navigate event should fire when traversing to a bfcache hit");
</script>