1) Should there be any special treatment for redirects upon reload? (originally brought up by @OrKoN)
2) What url should be set? The method returns without awaiting (unlike wait="interactive" and wait="complete"), therefore it's not possible to know the url at the time of the return. Some options:
return about:blank
return empty string
return the "current URL" (=same URL as the previous navigation): may not play well with redirects
3) What navigation should be set? As per the spec, it should be a new ID. But that ID may not be ready at the time of the return.
As per @juliandescottes:
However the HTML spec for navigate does not seem to accept a navigation id as optional parameter for navigate, and instead always generates one at step 6:
This issue is a direct follow-up of: https://github.com/w3c/webdriver-bidi/issues/527.
browsingContext.reload
was recently updated to returnNavigateResult
instead ofEmptyResult
.There are two keys: 1) url and 2) navigation.
We need to consider all the following scenarios:
1) Should there be any special treatment for redirects upon reload? (originally brought up by @OrKoN)
2) What
url
should be set? The method returns without awaiting (unlikewait="interactive"
andwait="complete"
), therefore it's not possible to know theurl
at the time of the return. Some options:about:blank
3) What
navigation
should be set? As per the spec, it should be a new ID. But that ID may not be ready at the time of the return.As per @juliandescottes: