@@ -337,63 +337,68 @@ <h2>
337337 </ ol >
338338 </ dd >
339339 </ dl >
340+ < section data-dfn-for ="MIDIOptions " data-link-for ="Navigator ">
341+ < h2 id ="MIDIOptions ">
342+ < dfn > MIDIOptions</ dfn > Dictionary
343+ </ h2 >
344+ < p >
345+ This dictionary contains optional settings that may be provided to
346+ the {{requestMIDIAccess()}} request.
347+ </ p >
348+ < pre class ="idl ">
349+ dictionary MIDIOptions {
350+ boolean sysex;
351+ boolean software;
352+ };
353+ </ pre >
354+ < dl >
355+ < dt >
356+ < dfn > sysex</ dfn >
357+ </ dt >
358+ < dd >
359+ < p >
360+ This member informs the system whether the ability to send and
361+ receive < a > System Exclusive</ a > messages is requested or allowed
362+ on a given {{MIDIAccess}} object. On the option passed to
363+ {{requestMIDIAccess()}}, if this member is set to true, but
364+ < a > System Exclusive</ a > support is denied (either by policy or by
365+ user action), the access request will fail with a
366+ {{"SecurityError"}} error. If this support is not requested (and
367+ allowed), the system will throw exceptions if the user tries to
368+ send < a > System Exclusive</ a > messages, and will silently mask out
369+ any < a > System Exclusive</ a > messages received on the port.
370+ </ p >
371+ </ dd >
372+ < dt >
373+ < dfn > software</ dfn >
374+ </ dt >
375+ < dd >
376+ < p >
377+ This member informs the system whether the ability to utilize any
378+ software synthesizers installed in the host system is requested
379+ or allowed on a given {{MIDIAccess}} object. On
380+ {{requestMIDIAccess()}}, if this member is set to true, but
381+ software synthesizer support is denied (either by policy or by
382+ user action), the access request will fail with a
383+ {{"SecurityError"}} error. If this support is not requested, the
384+ system should not include any software synthesizers in the
385+ {{MIDIAccess}} exposure of available ports.
386+ </ p >
387+ < p >
388+ Note that may result in a two-step request procedure if software
389+ synthesizer support is desired but not required - software
390+ synthesizers may be disabled when MIDI hardware device access is
391+ allowed.
392+ </ p >
393+ </ dd >
394+ </ dl >
395+ </ section >
340396 </ section >
341- < section data-dfn-for ="MIDIOptions " data-link-for ="Navigator ">
342- < h2 id ="MIDIOptions ">
343- < dfn > MIDIOptions</ dfn > Dictionary
344- </ h2 >
345- < p >
346- This dictionary contains optional settings that may be provided to
347- the {{requestMIDIAccess()}} request.
348- </ p >
349- < pre class ="idl ">
350- dictionary MIDIOptions {
351- boolean sysex;
352- boolean software;
353- };
354- </ pre >
355- < dl >
356- < dt >
357- < dfn > sysex</ dfn >
358- </ dt >
359- < dd >
360- < p >
361- This member informs the system whether the ability to send and
362- receive < a > System Exclusive</ a > messages is requested or allowed
363- on a given {{MIDIAccess}} object. On the option passed to
364- {{requestMIDIAccess()}}, if this member is set to true, but
365- < a > System Exclusive</ a > support is denied (either by policy or by
366- user action), the access request will fail with a
367- {{"SecurityError"}} error. If this support is not requested (and
368- allowed), the system will throw exceptions if the user tries to
369- send < a > System Exclusive</ a > messages, and will silently mask out
370- any < a > System Exclusive</ a > messages received on the port.
371- </ p >
372- </ dd >
373- < dt >
374- < dfn > software</ dfn >
375- </ dt >
376- < dd >
377- < p >
378- This member informs the system whether the ability to utilize any
379- software synthesizers installed in the host system is requested
380- or allowed on a given {{MIDIAccess}} object. On
381- {{requestMIDIAccess()}}, if this member is set to true, but
382- software synthesizer support is denied (either by policy or by
383- user action), the access request will fail with a
384- {{"SecurityError"}} error. If this support is not requested, the
385- system should not include any software synthesizers in the
386- {{MIDIAccess}} exposure of available ports.
387- </ p >
388- < p >
389- Note that may result in a two-step request procedure if software
390- synthesizer support is desired but not required - software
391- synthesizers may be disabled when MIDI hardware device access is
392- allowed.
393- </ p >
394- </ dd >
395- </ dl >
396- </ section >
397+ </ section >
398+ < section >
399+ < h2 >
400+ The MIDI API
401+ </ h2 >
397402 < section data-dfn-for ="MIDIInputMap ">
398403 < h3 id ="MIDIInputMap ">
399404 < dfn > MIDIInputMap</ dfn > Interface
@@ -1299,6 +1304,7 @@ <h2 id="MIDIConnectionEventInit">
12991304 </ dl >
13001305 </ section >
13011306 </ section >
1307+ </ section >
13021308 < section >
13031309 < h2 >
13041310 Security and Privacy Considerations of MIDI
0 commit comments