[stalgiag]

This lets WebDriver BiDi pass in the navigation ID it already generates so browsingContext.navigate can follow the navigation it started. See w3c/webdriver-bidi#858 and w3c/webdriver-bidi#1180.

• At least two implementers are interested (and none opposed):
  • Gecko
  • Chromium
• Tests are written and can be reviewed and commented upon at:
  • Only observable through BiDi: [wdspec] Test that browsingContext.navigate doesn't fire a navigate event web-platform-tests/wpt#63659
• Implementation bugs are filed:
  • Chromium: N/A
  • Gecko: N/A
  • WebKit: N/A
  • Deno (only for timers, structured clone, base64 utils, channel messaging, module resolution, web workers, and web storage): N/A
  • Node.js (only for timers, structured clone, base64 utils, channel messaging, and module resolution): N/A
• Corresponding HTML AAM & ARIA in HTML issues & PRs: N/A
• MDN issue is filed: N/A
• The top of this comment includes a clear commit message to use.

---

/browsing-the-web.html ( diff )