Navigation API: Save the persisted state before same-document reload

[noamr]

Closes web-platform-tests/wpt#60113

This reflects current chromium/webkit behavior.

• At least two implementers are interested (and none opposed):
  • Chromium
  • Assuming WebKit because it's already implemented
• Tests are written and can be reviewed and commented upon at: https://wpt.fyi/results/navigation-api/scroll-behavior (see tests currently failing only in Firefox)
• Implementation bugs are filed:
  • Chromium: Works
  • Gecko: …
  • WebKit: Works
  • Deno (only for timers, structured clone, base64 utils, channel messaging, module resolution, web workers, and web storage): …
  • Node.js (only for timers, structured clone, base64 utils, channel messaging, and module resolution): …
• The top of this comment includes a clear commit message to use.

(See WHATWG Working Mode: Changes for more details.)

---

/nav-history-apis.html ( diff )

[noamr]

@farre

[annevk]

Looks okay editorially.

For OP, if Deno/Node are not applicable, just remove those bullet points.

[farre]

If we're OK with doing it only for intercepted navigations, then this fits the bill. I'm OK with this, since that keeps the implementation scope down a fair bit.

[noamr]

If we're OK with doing it only for intercepted navigations, then this fits the bill. I'm OK with this, since that keeps the implementation scope down a fair bit.

At the very least that's what the tests cover? Correct me if I am wrong?