Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
OrKoN opened this issue Jan 16, 2025 · 3 comments · May be fixed by #861
Open

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

OrKoN opened this issue Jan 16, 2025 · 3 comments · May be fixed by #861

Comments

@OrKoN
Copy link
Contributor

OrKoN commented Jan 16, 2025

  • 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
Copy link
Member

jgraham commented Jan 16, 2025

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
Copy link
Contributor Author

OrKoN commented Jan 16, 2025

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
Copy link
Member

jgraham commented Jan 17, 2025

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

@OrKoN OrKoN linked a pull request Jan 17, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants