W3C home > Mailing lists > Public > public-audio@w3.org > October to December 2012

[Bug 20511] New: send(…, DOMHighResTimeStamp? timestamp)

From: <bugzilla@jessica.w3.org>
Date: Mon, 24 Dec 2012 08:26:09 +0000
To: public-audio@w3.org
Message-ID: <bug-20511-5429@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20511

            Bug ID: 20511
           Summary: send(…, DOMHighResTimeStamp? timestamp)
    Classification: Unclassified
           Product: AudioWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: MIDI API
          Assignee: dave.null@w3.org
          Reporter: w3c@marcosc.com
        QA Contact: public-audio@w3.org

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

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 24 December 2012 08:26:10 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:04 UTC