[encrypted-media-2] Missing tasks in parallel steps in Encrypted Media Extensions

[dontcallmedom-bot]

While crawling Encrypted Media Extensions, 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 Navigator/requestMediaKeySystemAccess() algorithm resolves/rejects a promise directly in a step that runs in parallel
• The MediaKeySystemAccess/createMediaKeys() algorithm resolves/rejects a promise directly in a step that runs in parallel
• The MediaKeys/setServerCertificate() algorithm resolves/rejects a promise directly in a step that runs in parallel
• The MediaKeySession/generateRequest() algorithm resolves/rejects a promise directly in a step that runs in parallel
• The MediaKeySession/load() algorithm resolves/rejects a promise directly in a step that runs in parallel
• The MediaKeySession/update() algorithm resolves/rejects a promise directly in a step that runs in parallel
• The HTMLMediaElement/setMediaKeys() 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.}