Missing tasks in parallel steps in Background Fetch

[dontcallmedom-bot]

While crawling Background Fetch, the following algorithms fire an event, or resolve or reject a Promise, within a step that runs in parallel without first queuing a task:

• [ ] The create record objects algorithm resolves/rejects a promise directly in a step that runs in parallel (steps 2.8.3 and 2.8.4)
• [ ] The get(id) algorithm resolves/rejects a promise directly in a step that runs in parallel
• [ ] The getIds() algorithm resolves/rejects a promise directly in a step that runs in parallel
• [ ] The abort() algorithm resolves/rejects a promise directly and throws an exception in a step that runs in parallel
• [ ] The updateUI(options) algorithm resolves/rejects a promise directly in a step that runs in parallel

See Dealing with the event loop in the HTML specification for guidance on how to deal with algorithm sections that run in parallel.

_{Cc @dontcallmedom @tidoust}

_{This issue was detected and reported semi-automatically by Strudy based on data collected in webref.}