BrowsingContext.navigate and BrowsingContext.reload should have navigation value even in case of wait: none.
In BiDi, the `await a navigation step generates a new navigation UUID for each navigation disregard of the wait condition. Even in case of same document fragment navigation.
In CDP:
Page.navigate's loaderId is omitted in case of same-document navigation, as the previously committed loaderId would not change.
Page.reload does not provide any loaderId. The loaderId can be retrieved only from the Page.lifecycleEvent of from the network events.
Currently, the navigation is not provided in case of reloading with wait none or same-document navigation.
thiagowfx
commented
11 months ago
BrowsingContext.navigateandBrowsingContext.reloadshould havenavigationvalue even in case ofwait: none.In BiDi, the `await a navigation step generates a new
navigationUUID for each navigation disregard of the wait condition. Even in case of same document fragment navigation.In CDP:
loaderIdis omitted in case of same-document navigation, as the previously committed loaderId would not change.loaderId. TheloaderIdcan be retrieved only from thePage.lifecycleEventof from the network events.Currently, the
navigationis not provided in case of reloading with waitnoneor same-document navigation.WPT tests: https://wpt.fyi/results/webdriver/tests/bidi/browsing_context/navigate/hash.py?label=master&label=experimental&aligned