- The Web Midi API is a [=powerful feature=] that is identified + The Web MIDI API is a [=powerful feature=] that is identified by the [=powerful feature/name=] "midi". It integrates with [[[Permissions]]] by defining the following permission-related flags:
@@ -248,7 +238,7 @@- The Web Midi API defines a [=policy-controlled feature=] named + The Web MIDI API defines a [=policy-controlled feature=] named "midi" which has a [=policy-controlled feature/default allowlist=] of `'self'`.
@@ -444,10 +434,10 @@- Note that may result in a two-step request procedure if software - synthesizer support is desired but not required - software - synthesizers may be disabled when MIDI hardware device access is - allowed. + Note that this may result in a two-step request procedure if + software synthesizer support is desired but not required - + software synthesizers may be disabled when MIDI hardware device + access is allowed.
@@ -532,7 +522,7 @@- This [=event handler=], of type {{MIDIConnectionEvent}}, MUST be + This [=event handler=], of type "statechange", MUST be supported by all objects implementing the {{MIDIAccess}} interface.
@@ -686,10 +676,10 @@
Makes the [=MIDI device=] corresponding to the {{MIDIPort}}
explicitly available. Note that this call is NOT required in order
- to use the {{MIDIPort}}- calling send() on a
+ to use the {{MIDIPort}} - calling send() on a
{{MIDIOutput}}, attaching a MIDIMessageEvent {{EventHandler}} on a
{{MIDIInput}}, or adding a MIDIMessageEvent {{EventListener}} on a
- {{MIDIInput}} will cause an implicit open(). The underlying
+ {{MIDIInput}} will cause an implicit open(). The underlying
implementation may not need to do anything in response to this
call. However, some underlying implementations may not be able to
support shared access to [=MIDI devices=], so using explicit
@@ -709,7 +699,7 @@
If access to a connected port is not available (for example, the port is already in use in an exclusive-access-only platform), the - Promise is rejected (if any) is invoked. + Promise is rejected.
If open() is called on a port that is
supported by all objects implementing {{MIDIInput}} interface.
- If the handler is set and the state attribute is not
- "opened", underlying implementation tries to make
- the port available, and change the state attribute to
- "opened". If succeeded, {{MIDIConnectionEvent}} is
- delivered to the corresponding MIDIPort and
- {{MIDIAccess}}.
+ If the handler is set and the {{MIDIPort/connection}} attribute
+ is not "open", the
+ underlying implementation tries to make the port available, and
+ change the {{MIDIPort/connection}} attribute to
+ "open". If
+ succeeded, {{MIDIConnectionEvent}} is delivered to the
+ corresponding {{MIDIPort}} and {{MIDIAccess}}.
If data is a [=System Exclusive=] message, and the
{{MIDIAccess}} did not enable [=System Exclusive=] access, throw
- an NotAllowedError exception.
+ a NotAllowedError exception.
If the port is either explicitly (through {{MIDIPort.open()}}) or implicitly (by adding a midimessage event handler on an input port, or calling {{MIDIOutput.send()}} - on an output port, this should be the default state of the device. + on an output port), this should be the default state of the + device.
An event object implementing this interface is passed to a
{{MIDIInput}}'s onmidimessage handler when [=MIDI messages=] are
- received. Note that the DOM {{Event}} timeStamp
+ received. Note that the DOM {{Event}} timeStamp
attribute is defined as a {{DOMHighResTimeStamp}}, and represents the
- high-resolution time of when the event was received or is to be sent.
+ high-resolution time of when the event was received.
[SecureContext, Exposed=(Window,Worker)]
@@ -1430,7 +1422,7 @@
- In order to enable to the above attack, a [=MIDI device=]
+ In order to enable the above attack, a [=MIDI device=]
would need all of the following to be true: