-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
File report on Missing tasks in parallel steps in WebDriver
strudy-bot
committed
Jan 30, 2025
1 parent
af2b5a0
commit bdc627c
Showing
1 changed file
with
15 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
--- | ||
Title: Missing tasks in parallel steps in WebDriver | ||
Tracked: N/A | ||
Repo: 'https://github.com/w3c/webdriver' | ||
--- | ||
|
||
While crawling [WebDriver](https://w3c.github.io/webdriver/), the following algorithms fire an event, or resolve or reject a Promise, within a step that runs [in parallel](https://html.spec.whatwg.org/multipage/infrastructure.html#in-parallel) without first queuing a task: | ||
* [ ] The algorithm that starts with "The remote end steps, given session, URL variables and parameters are:" resolves/rejects a promise directly in a step that runs in parallel | ||
* [ ] The algorithm that starts with "The remote end steps, given session, URL variables and parameters are:" resolves/rejects a promise directly in a step that runs in parallel | ||
|
||
See [Dealing with the event loop](https://html.spec.whatwg.org/multipage/webappapis.html#event-loop-for-spec-authors) in the HTML specification for guidance on how to deal with algorithm sections that run *in parallel*. | ||
|
||
<sub>Cc @dontcallmedom @tidoust</sub> | ||
|
||
<sub>This issue was detected and reported semi-automatically by [Strudy](https://github.com/w3c/strudy/) based on data collected in [webref](https://github.com/w3c/webref/).</sub> |