Skip to content

Pass a new "hasImmediateNavigationForWebDriver" flag to the "WebDriver BiDi navigable created" event. - #12833

Draft
lutien wants to merge 1 commit into
whatwg:mainfrom
lutien:pass-hasStartedNavigatingForWebDriver-to-WebDriver-BiDi-navigable-created
Draft

Pass a new "hasImmediateNavigationForWebDriver" flag to the "WebDriver BiDi navigable created" event.#12833
lutien wants to merge 1 commit into
whatwg:mainfrom
lutien:pass-hasStartedNavigatingForWebDriver-to-WebDriver-BiDi-navigable-created

Conversation

@lutien

@lutien lutien commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Create a new hasImmediateNavigationForWebDriver flag to indicate if a navigable is going to perform a navigation beyond "about:blank" and the client will have to wait for load events to make sure that the navigable is ready to be interacted with. In case of lazy iframes the hasImmediateNavigationForWebDriver has to be set to true if an iframe will navigate to non-about:blank page and it its node intersects with the viewport.

  • 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.)


/document-sequences.html ( diff )
/form-control-infrastructure.html ( diff )
/iframe-embed-object.html ( diff )
/links.html ( diff )
/nav-history-apis.html ( diff )
/obsolete.html ( diff )

…r BiDi navigable created" event.

Create a new "hasStartedNavigatingForWebDriver" flag to indicate if a navigable is going to perform a navigation beyond "about:blank" and client will have to wait for load events to make sure that the navigable is ready to be interected with. In case of lazy iframes the "hasStartedNavigatingForWebDriver" has to be set to true if an iframe is going to navigate to non-about:blank page and it its node intersects with the viewport.
@lutien
lutien force-pushed the pass-hasStartedNavigatingForWebDriver-to-WebDriver-BiDi-navigable-created branch from 8d3f6a8 to f206b4d Compare August 26, 2026 12:44
@lutien lutien changed the title Pass a new "hasStartedNavigatingForWebDriver" flag to the "WebDriver BiDi navigable created" event. Pass a new "hasImmediateNavigationForWebDriver" flag to the "WebDriver BiDi navigable created" event. Aug 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant