Re: Bug 20221 - Define mechanism for creating PointerEvent instances

Just for the record, we talked about this on the call today and we think
there is a functional difference that could prevent implementations from
implementing this using inheritance:
http://dev.w3.org/2006/webapi/WebIDL/#idl-dictionaries.

Jacob is going to investigate further, and if confirmed then we'll take a
dependency on DOM4 events.   Draft minutes here for anyone that wants to
see the discussion: http://www.w3.org/2012/12/18-pointerevents-minutes.html.

Rick


On Tue, Dec 18, 2012 at 10:30 AM, Olli Pettay <Olli.Pettay@helsinki.fi>wrote:

> 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<https://www.w3.org/Bugs/Public/show_bug.cgi?id=20221>
>>
>>
>>
>>
>