if navigation is triggered then chromedriver should wait for navigation to complete in the following scenarios:
it would probably be easiest to implement this as an explicit function first. ex.
driver.waitForNavigation((driver) => {
myFavoriteLinkNode.click()
})this could also be implicit in our actions but it would have some overhead. we would need to wait at least xms for the navigation to start.
another approach would be to proxy the Driver and Node object and wait for navigation when Page.frameStartedLoading event is triggered on the top level frame. i'll give this approach a shot after i complete basic frame and window handling.
if navigation is triggered then chromedriver should wait for navigation to complete in the following scenarios:
user clicks on a node
user sends keys to a node
it would probably be easiest to implement this as an explicit function first. ex.
this could also be implicit in our actions but it would have some overhead. we would need to wait at least xms for the navigation to start.
another approach would be to proxy the
DriverandNodeobject and wait for navigation whenPage.frameStartedLoadingevent is triggered on the top level frame. i'll give this approach a shot after i complete basic frame and window handling.