File: README.md

package info (click to toggle)
firefox-esr 128.14.0esr-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 4,230,180 kB
  • sloc: cpp: 7,104,278; javascript: 6,088,450; ansic: 3,654,017; python: 1,212,326; xml: 594,604; asm: 420,652; java: 182,969; sh: 71,124; makefile: 20,747; perl: 13,449; objc: 12,399; yacc: 4,583; cs: 3,846; pascal: 2,973; lex: 1,720; ruby: 1,194; exp: 762; php: 436; lisp: 258; awk: 247; sql: 66; sed: 54; csh: 10
file content (26 lines) | stat: -rw-r--r-- 1,095 bytes parent folder | download | duplicates (18) 
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
 
# Navigation API ordering/transition tests

These are meant to test the ordering between various events and promises, as
well as in some cases how the `navigation.transition` values changes.

Some of them use the `Recorder` framework in `resources/helpers.mjs`, and others
test tricky cases (e.g. reentrancy) in a more ad-hoc way.

<https://github.com/WICG/navigation-api/#complete-event-sequence> is a useful
reference for the intent of these tests.

Note:

* Variants specifically exist for `currententrychange` because an event listener
  existing for `currententrychange` causes code to run, and thus microtasks to run,
  at a very specific point in the navigation-commit lifecycle. We want to test
  that it doesn't impact the ordering.
* Similarly we test that `intercept()` does not change
  the ordering compared to no `intercept()` call, for same-document
  navigations, by trying to ensure most variants have appropriate
  `intercept()` counterparts with similar orderings.

TODOs:

* Also test `popstate` and `hashchange` once
  <https://github.com/whatwg/html/issues/1792> is fixed.