Navigate and reload calls are out of sync with the HTML spec?

[OrKoN]

• WebDriver BiDi spec uses the value "default" as history handling. HTML spec has auto/replace/push only.
• WebDriver BiDi spec uses the value "reload" as history handling. HTML spec does not support it.

Should we use "auto" for history handling in navigate and call https://html.spec.whatwg.org/multipage/browsing-the-web.html#reload to specify the reload command?

cc @jgraham @sadym-chromium

[jgraham]

I suspect the key thing we want is to use the browser UI value for user navigation involvement in both the navigate and reload algorithms. Otherwise I we want to use the default values for parameters. This matches the browser UI requirements in https://html.spec.whatwg.org/multipage/document-lifecycle.html#nav-traversal-ui

[OrKoN]

Also, I think a navigation ID is not a parameter accepted by the HTML spec. We should probably use https://html.spec.whatwg.org/multipage/browsing-the-web.html#ongoing-navigation.

[jgraham]

Yes, it looks like HTML wants to handle creating the ID now.

[domenic]

I apologize that we messed up this integration. If you need something from the HTML spec to let you generate navigation IDs and pass them in, that should not be a problem.

[OrKoN]

I think a bigger problem is that WebDriver BiDi spec currently assumes that page reloads are behaving like regular spec navigations resulting "navigation started" and other events as instrumented in https://html.spec.whatwg.org/#navigate. So what is considered to be a navigation has different meanings in the HTML and WebDriver BiDi specs, I think WebDriver BiDi is closer to what is documented in this note https://html.spec.whatwg.org/#navigating-across-documents:navigate-2 (only in terms of reloads and traversals, the history updates are also separate in WebDriver)