WebAudio/web-midi-api Issues

Last updated Oct 7, 2025, 5:48:05 AM UTC.

5 issues with out-of-SLO pending edits
7 out-of-SLO soon-priority issues

Need Edits

Try to apply the edits requested in these issues within 2 weeks. [ More Info ] [ See these issues on Github ]

Issue	Title	Within SLO	Has needed edits for	Time left	Time past SLO
#48	Does MIDIPort.id need to be origin-scoped and/or regenerated with cookies?	❌	10.3 years		10.3 years
#231	Are `MIDIInputPort` and `MIDIOutputPort` populated during `requestMIDIAccess` ?	❌	2 years		2 years
#210	Change the MIDIOutput.send() spec to allow raising a RangeError when the passed ArrayBuffer is too big	❌	2 years		2 years
#136	Sysex access information in MIDIPort?	❌	1 year		12 months
#220	Rewrite requestMIDIAccess to hook into permissions	❌	8.4 months		8 months

Soon

Try to resolve soon-priority issues within 91 days. [ More Info ] [ See these issues on Github ]

Issue	Title	Within SLO	On maintainers' plates for	Time left	Time past SLO
#136	Sysex access information in MIDIPort?	❌	10.3 months		7.3 months
#232	midi clock support?	❌	10.3 months		7.3 months
#210	Change the MIDIOutput.send() spec to allow raising a RangeError when the passed ArrayBuffer is too big	❌	10.3 months		7.3 months
#220	Rewrite requestMIDIAccess to hook into permissions	❌	10.3 months		7.3 months
#231	Are `MIDIInputPort` and `MIDIOutputPort` populated during `requestMIDIAccess` ?	❌	10.3 months		7.3 months
#48	Does MIDIPort.id need to be origin-scoped and/or regenerated with cookies?	❌	10.3 months		7.3 months
#158	Backpressure exposure for asynchronous send()	❌	10.3 months		7.3 months