This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
For send()'s second argument, the spec says that it takes DOMHighResTimeStamp… however, "DOMHighResTimeStamp" isn't a "real data type" (in that there is no way to actually force a type check on it in some meaningful way AFAICT). Hence, it's actually just a double that is relative to some start time. This is confirmed in [1]: typedef double DOMHighResTimeStamp; To avoid confusion during implementation, I would suggest changing the value data type of the second argument of the send() method to a double. optional double timestamp; Also, why is the second argument nullable when it's already optional? Note that the current text in the spec is redundant because WebIDL already handles the type checking. Please remove " or if timestamp is passed but is not a valid DOMHighResTimeStamp, throw a TYPE_ERROR exception". [1] http://www.w3.org/TR/2012/REC-hr-time-20121217/#domhighrestimestamp
Resolved with https://github.com/WebAudio/web-midi-api/commit/23d1a3f64c003ff49077f1a7c6477f109f1d53b9. Use "double" for all references to DOMHighResTimeStamp parameters.
Batch-closing RESOLVED MIDI issues. Reminder: midi issues now tracked at https://github.com/WebAudio/web-midi-api/issues