Open
Description
When running the driver, I was able to deadlock it by calling driver.get(url) while the runAsyncRunning_ was already set to true.
The driver ended up in an endless loop and whatever originally set the field to true never finished (or was interrupted).
I'm wondering what the reason is to wait for async when calling driver.get, as ideally I would expect the driver to drop everything it was doing (and ignore any background javascript or other async tasks) and immediately open the new page.
Or is this standard behavior on other browsers as well where opening a new url in the same window is delayed until background tasks finish?
Metadata
Metadata
Assignees
Labels
No labels
Activity