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

Re: [Web MIDI API] timeStamp and timestamp

From: Marcos Caceres <marcosscaceres@gmail.com>
Date: Tue, 18 Dec 2012 08:12:45 +0000
Message-Id: <D6E06635-989D-4784-818F-051C0FD915F1@gmail.com>
Cc: "public-audio@w3.org" <public-audio@w3.org>, Ms2ger <ms2ger@gmail.com>, Cameron McCormack <cam@mcc.id.au>
To: Jussi Kalliokoski <jussi.kalliokoski@gmail.com>

On 17 Dec 2012, at 14:35, Jussi Kalliokoski <jussi.kalliokoski@gmail.com> wrote:

> On Sun, Dec 16, 2012 at 10:09 AM, Marcos Caceres <marcosscaceres@gmail.com> wrote:
>> > Additionally, MIDIEvent defines a data attribute:
>> > readonly attribute Uint8Array data;
>> >
>> > IIRC, there has also been talk of adding a 'data' attribute directly on the DOMEvent interface (with and any type). Not sure how far along that proposal has come along. Ms2ger, any idea?
>> Argh, seems I confused 'data' with 'detail' (from CustomEvent).. anyway, same thing.
> I doubt the "data" attribute is a problem, after all it's fairly consistent with other "onmessage" events around the platform (Web Workers, Window.{postMessage,onmessage}, WebSockets, MessageChannel and so on).

Fair enough. I was trying to see if we could get rid of MIDIEvent altogether and just use Event, but that seems unlikely. 
Received on Tuesday, 18 December 2012 08:13:42 UTC

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