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

[Bug 20411] New: timestamp in MIDIEvent in odds with DOM4 Event timeStamp?

From: <bugzilla@jessica.w3.org>
Date: Mon, 17 Dec 2012 14:26:23 +0000
To: public-audio@w3.org
Message-ID: <bug-20411-5429@http.www.w3.org/Bugs/Public/>

            Bug ID: 20411
           Summary: timestamp in MIDIEvent in odds with DOM4 Event
    Classification: Unclassified
           Product: AudioWG
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: MIDI API
          Assignee: dave.null@w3.org
          Reporter: jussi.kalliokoski@gmail.com
        QA Contact: public-audio@w3.org

[ Marcos Caceres wrote ]

DOM4 Event defines:
readonly attribute DOMTimeStamp timeStamp;

While MIDIEvent [1] defines timestamp:
readonly attribute DOMHighResTimeStamp timestamp;

I think that is going to lead to confusion. Perhaps it might be worth talking
to the WebIDL people and getting them to up the precision of DOMTimeStamp? Or
easier to just rename the MIDIEvent attribute? Cameron, thoughts?

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 17 December 2012 14:26:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:14 UTC