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

Re: [Web MIDI API] timeStamp and timestamp

From: Jussi Kalliokoski <jussi.kalliokoski@gmail.com>
Date: Mon, 17 Dec 2012 16:40:18 +0200
Message-ID: <CAJhzemUz6Zcd5W0XStjyrmBUXveF2A_z=y+SWqX2rSkbmEOZQQ@mail.gmail.com>
To: Marcos Caceres <marcosscaceres@gmail.com>
Cc: "public-audio@w3.org" <public-audio@w3.org>, Ms2ger <ms2ger@gmail.com>, Cameron McCormack <cam@mcc.id.au>
On Mon, Dec 17, 2012 at 4:35 PM, 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).
>

Oh, and I filed an issue for the timestamp <-> timeStamp problem:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20411
Received on Monday, 17 December 2012 14:40:46 UTC

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