Missing tasks in parallel steps in Cookie Store API

[dontcallmedom-bot]

While crawling Cookie Store API, 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 CookieStore/get(name) algorithm resolves/rejects a promise directly in a step that runs in parallel
• The CookieStore/get(options) algorithm resolves/rejects a promise directly in a step that runs in parallel
• The CookieStore/getAll(name) algorithm resolves/rejects a promise directly in a step that runs in parallel
• The CookieStore/getAll(options) algorithm resolves/rejects a promise directly in a step that runs in parallel
• The CookieStore/set(name, value) algorithm resolves/rejects a promise directly in a step that runs in parallel
• The CookieStore/set(options) algorithm resolves/rejects a promise directly in a step that runs in parallel
• The CookieStore/delete(name) algorithm resolves/rejects a promise directly in a step that runs in parallel
• The CookieStore/delete(options) algorithm resolves/rejects a promise directly in a step that runs in parallel
• The CookieStoreManager/subscribe(subscriptions) algorithm resolves/rejects a promise directly in a step that runs in parallel
• The CookieStoreManager/getSubscriptions() algorithm resolves/rejects a promise directly in a step that runs in parallel
• The CookieStoreManager/unsubscribe(subscriptions) 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.}