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

Re: Bug 20221 - Define mechanism for creating PointerEvent instances

From: Olli Pettay <Olli.Pettay@helsinki.fi>
Date: Tue, 18 Dec 2012 17:30:25 +0200
Message-ID: <50D08C11.1000404@helsinki.fi>
To: Jacob Rossi <Jacob.Rossi@microsoft.com>, "Rick Byers (rbyers@google.com)" <rbyers@google.com>, "public-pointer-events@w3.org" <public-pointer-events@w3.org>
On 12/18/2012 08:23 AM, Jacob Rossi wrote:
> Hey Rick,
>
> Took a look at this issue [1].  Following the convention set up in the DOM4 Events proposal is the right way to go. But I don't want it to depend
> on that spec as hasn't been formally adopted yet by the W3C (and would gate this spec if we normatively depend on it).  So instead, how does this
> additional IDL look?
Looks ok. The dictionary is ofc a bit ugly, but implementations are free to implement it using inheritance.

>
> [Constructor(DOMString type, optional PointerEventInit eventInitDict)] interface PointerEvent:MouseEvent { ... }
>
> dictionary PointerEventInit { boolean bubbles; boolean cancelable; views::AbstractView view long detail; long screenX; long screenY; long clientX;
> long clientY; boolean ctrlKey; boolean shiftKey; boolean altKey; boolean metaKey; unsigned short button; unsigned short buttons; EventTarget
> relatedTarget; long pointerId; long width; long  height; float pressure; long tiltX; long tiltY; DOMString pointerType; unsigned long long
> hwTimestamp; boolean isPrimary; }
>
> -Jacob
>
> [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=20221
>
>
>
Received on Tuesday, 18 December 2012 15:30:57 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:20:24 UTC