MIDI APIs now use NotAllowedError instead of SecurityError

[nikelborm]

Motivation

From issue WebAudio/web-midi-api#261

webaudio.github.io/web-midi-api#dom-navigator-requestmidiaccess

At the moment a SecurityError (The operation is insecure.) is thrown when a user rejects a permissions prompt for MIDI access requested through the requestMIDIAccess() method, but it would make more sense to use a NotAllowedError (The request is not allowed by the user agent or the platform in the current context, possibly because the user denied permission.) for this.

Related issues and pull requests

The change in spec: WebAudio/web-midi-api@b7806b8
According to PR: WebAudio/web-midi-api#267

[github-actions]

Preview URLs

• /en-US/docs/Web/API/Navigator/requestMIDIAccess
• /en-US/docs/Web/HTTP/Reference/Headers/Permissions-Policy/midi

Flaws (3)

Note! 1 document with no flaws that don't need to be listed. 🎉

URL: /en-US/docs/Web/HTTP/Reference/Headers/Permissions-Policy/midi
Title: Permissions-Policy: midi directive
Flaw count: 3

• unknown:
  • No generic content config found
  • no blog root
  • no blog root

[sideshowbarker]

@nikelborm, congrats on landing your first docs change here — welcome aboard 🎉