- From: <bugzilla@jessica.w3.org>
- Date: Wed, 26 Dec 2012 17:58:11 +0000
- To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20510 --- Comment #10 from Marcos Caceres <w3c@marcosc.com> --- (In reply to comment #9) > That sounds more directive to me. :) Ok, but the WebIDL bit is important here... in section 7.3.1 Methods, the spec has wording about how to send() messages that might conflict with WebIDL. For example: "If data is not a valid sequence, does not contain a valid MIDI message, or if timestamp is passed but is not a valid DOMHighResTimeStamp, throw a TYPE_ERROR exception." 1. "valid MIDI message" is not defined, AFACT. 2. and this is not needed, as it's handled by WebIDL: "if timestamp is passed but is not a valid DOMHighResTimeStamp, throw a TYPE_ERROR exception." (I think I already filed 2. above) Also: "The data MUST contain one or more valid, complete MIDI messages. Running status is not allowed in the data, as underlying systems may not support it." 1. Data is not a "conformance class", hence an RFC2119 keyword cannot be used there. Please change it to: "The data contains one or more MIDI messages." The above is a statement of fact (which may or may not be true, but that is irrelevant until processed). 2. It's unclear what "Running status is not allowed in the data" means. There is no algorithm defined in the specification to check for this (and do something if "running status" is found). -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 26 December 2012 17:58:12 UTC