Update report on Missing tasks in parallel steps in Web Cryptography API

[dontcallmedom-bot]

This pull request was automatically created by Strudy upon detecting errors in Missing tasks in parallel steps in Web Cryptography API.

Similar errors had already been detected. Please check that the diff is correct, and that the errors have not already been reported in https://github.com/w3c/webcrypto.

If everything is OK, you can merge this pull request which will report the issue below to the repo, and update the underlying report file with a link to the said issue.

---

Title: Missing tasks in parallel steps in Web Cryptography API
Tracked: >-
Unconventional usage of "throw", see
w3c/webcrypto#386 (comment)
Repo: 'https://github.com/w3c/webcrypto'

While crawling Web Cryptography 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 SubtleCrypto/encrypt() algorithm resolves/rejects a promise directly in a step that runs in parallel
• The SubtleCrypto/decrypt() algorithm resolves/rejects a promise directly in a step that runs in parallel
• The SubtleCrypto/sign() algorithm resolves/rejects a promise directly in a step that runs in parallel
• The SubtleCrypto/verify() algorithm resolves/rejects a promise directly in a step that runs in parallel
• The SubtleCrypto/digest() algorithm resolves/rejects a promise directly in a step that runs in parallel
• The SubtleCrypto/generateKey() algorithm resolves/rejects a promise directly in a step that runs in parallel
• The SubtleCrypto/deriveKey() algorithm resolves/rejects a promise directly in a step that runs in parallel
• The SubtleCrypto/deriveBits() algorithm resolves/rejects a promise directly in a step that runs in parallel
• The SubtleCrypto/importKey() algorithm resolves/rejects a promise directly in a step that runs in parallel
• The SubtleCrypto/exportKey() algorithm resolves/rejects a promise directly in a step that runs in parallel
• The SubtleCrypto/wrapKey() algorithm resolves/rejects a promise directly in a step that runs in parallel
• The SubtleCrypto/unwrapKey() 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.}