Fix the event variable in the navigation interception example - #13133

Use e.destination.url in the navigation interception example. The listener parameter and all other event accesses in that example use e.

This avoids relying on the legacy global event property.

Spec: https://html.spec.whatwg.org/multipage/nav-history-apis.html#navigation-api-intro

• At least two implementers are interested (and none opposed):
  • …
  • …
• Tests are written and can be reviewed and commented upon at:
  • …
• Implementation bugs are filed:
  • Chromium: …
  • Gecko: …
  • WebKit: …
  • 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): …
• Corresponding HTML AAM & ARIA in HTML issues & PRs:
• MDN issue is filed: …
• 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 )