This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
From Marcos: It would be better if you could fold everything into MIDIPort and get rid of MIDIOutput and MIDIInput? you already have the port type, and you can just say that sending() does nothing when a port is not outputting. If you don't agree, then I think MIDIInput and MIDIOutput need to inherit from MIDIPort (not implement the interface). Implementing the interface makes a huge mess when actually implementing, as the stuff from MIDIPort has to be copied over from MIDIPort. So, worst case, please change the spec to match the following pattern: interface MIDIOutput : MIDIPort { } interface MIDIInput : MIDIPort { } MIDIPort : EventTarget{ } However, I strongly urge you to do away with MIDIInput and MIDIOutput. They are redundant, IMHO.
I'll restructure. They are not redundant, though - Input and Output ports are very different, and not interchangeable.
Forgot this bit of feedback to roll together: The following is also incorrect: [TreatNonCallableAsNull] attribute callback? onmessage; Please change it to: attribute EventHandler onmessage; Fixed all these issues: https://dvcs.w3.org/hg/audio/rev/477c4b064f31
Batch-closing RESOLVED MIDI issues. Reminder: midi issues now tracked at https://github.com/WebAudio/web-midi-api/issues