Handle the case where a navigation happens during script execution
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
Let completion be Function.[[Call]](window, parameters) with function as the this value.
During this step a navigation can happen which will prevent the function completing and so prevent the command ever returning. For async scripts the situation is even worse because the navigation can occur any time before the completion callback is called.
We should explicitly state somewhere that if the browsing context becomes inactive during script execution then we respond with a Javascript Error (or maybe No Such Window?)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the script-execution completion step described in this issue and trace how navigation affects synchronous and asynchronous script execution. Decide whether the specified response should be Javascript Error or No Such Window, then update the relevant WebDriver specification text and verify that both execution cases are covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100