Skip to content

Commit

Permalink
File report on Missing tasks in parallel steps in Web Background Sync…
Browse files Browse the repository at this point in the history
…hronization
  • Loading branch information
strudy-bot authored and dontcallmedom committed Sep 9, 2024
1 parent b263649 commit 46c3a9b
Showing 1 changed file with 16 additions and 0 deletions.
16 changes: 16 additions & 0 deletions issues/background-sync-missingtask.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
---
Title: Missing tasks in parallel steps in Web Background Synchronization
Tracked: N/A
Repo: 'https://github.com/WICG/background-sync'
---

While crawling [Web Background Synchronization](https://wicg.github.io/background-sync/spec/), 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 [SyncManager/register(tag)](https://wicg.github.io/background-sync/spec/#dom-syncmanager-register) algorithm resolves/rejects a promise directly in a step that runs in parallel
* [ ] The [SyncManager/getTags()](https://wicg.github.io/background-sync/spec/#dom-syncmanager-gettags) algorithm resolves/rejects a promise directly in a step that runs in parallel
* [ ] The [fire a sync event](https://wicg.github.io/background-sync/spec/#fire-a-sync-event) algorithm fires an event 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>

0 comments on commit 46c3a9b

Please sign in to comment.