Missing tasks in parallel steps in Web Cryptography API

[dontcallmedom-bot]

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/sign() 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.}