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

https://www.w3.org/Bugs/Public/show_bug.cgi?id=20411

--- Comment #1 from Jussi Kalliokoski <jussi.kalliokoski@gmail.com> ---
(In reply to comment #0)
> [ 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?

Hmm, I doubt upping the precision of DOMTimeStamp makes sense for the use cases
it serves. I think it's a better idea to rename the timestamp to something less
ambiguous, but my best (and worst) idea for now is "MIDITimeStamp" (I have no
preference on the casing), but that's not very appealing.

But I agree, it's confusing to have "timestamp" and "timeStamp" that may differ
in times and in precision.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 17 December 2012 14:30:43 UTC