MIDI APIs now use NotAllowedError instead of InvalidAccessError

[nikelborm]

Motivation

Quoted from WebAudio/web-midi-api#278 PR description:

According to Web IDL spec on InvalidAccessError:

Deprecated. Use TypeError for invalid arguments, "NotSupportedError" DOMException for unsupported operations, and "NotAllowedError" DOMException for denied requests instead.

Previously, while trying to open MIDIPort, "InvalidAccessError" DOMException was thrown when...

the device is unavailable (e.g., is already in use by another process and cannot be opened, or is disconnected)

In this case, I believe NotAllowedError fits well, according to its Web IDL spec description:

The request is not allowed by the user agent or the platform in the current context, possibly because the user denied permission.

Security and permissions reasons are only a subset of the appropriate causes, according to this definition. An attempt to open the port can fail. Somebody's exclusive lock on the port, or the port being disconnected, is the current context driving the platform's decision not to allow the operation.

And in the context of forbidden .send calls:

If data is a System Exclusive message, and the MIDIAccess did not enable System Exclusive access, throw an InvalidAccessError exception.

NotAllowedError fits even better, because it fits an explicitly defined subset of permission errors.

Related issues and pull requests

The change in spec: WebAudio/web-midi-api@3795f22

This PR should not be confused with #41956, which talks about SecurityErrors instead

[github-actions]

Preview URLs

• /en-US/docs/Web/API/MIDIOutput/send
• /en-US/docs/Web/API/MIDIPort/open

Flaws (2)

URL: /en-US/docs/Web/API/MIDIOutput/send
Title: MIDIOutput: send() method
Flaw count: 1

• broken_links:
  • /en-US/docs/Web/Security/Secure_Contexts is a redirect

---

URL: /en-US/docs/Web/API/MIDIPort/open
Title: MIDIPort: open() method
Flaw count: 1

• broken_links:
  • /en-US/docs/Web/Security/Secure_Contexts is a redirect