W3C home > Mailing lists > Public > public-pointer-events@w3.org > January to March 2014

Re: "List of Pointer Events" table default actions

From: Rick Byers <rbyers@google.com>
Date: Tue, 21 Jan 2014 11:38:39 -0500
Message-ID: <CAFUtAY-Yq+qsn6Sb+SphhSSdWJMDwmVKJHnWK5jt9SjGZXduOQ@mail.gmail.com>
To: "Patrick H. Lauke" <redux@splintered.co.uk>
Cc: "public-pointer-events@w3.org" <public-pointer-events@w3.org>
Thanks Patrick!  Normally we just discuss potential changes over e-mail
(although in the past the changes have been simple enough that it's easy to
just include the proposed text in e-mail, possibly not the case here).
 There is a bug tracker -
https://www.w3.org/Bugs/Public/describecomponents.cgi?product=PointerEventsWG.
 You could file a new bug and put details there if you like.

Since the compatibility mouse events stuff is listed as optional, I think
it would be better to avoid complicating 5.2.1 much for them and instead
leave the discussion to section 11.  Your "If the pointer is primary ..."
note sounds good to me.

I don't really have a strong preference on the ordering - I do like that
your proposed ordering focuses on the order events are typically seen in
practice instead of the logical grouping.

Rick


On Sun, Jan 19, 2014 at 8:01 PM, Patrick H. Lauke <redux@splintered.co.uk>wrote:

> On 20/01/2014 00:36, Patrick H. Lauke wrote:
>
>> In the meantime, I had an initial thought about 5.2.1 - see the fragment
>> I put up on
>> https://dl.dropboxusercontent.com/u/48771/pointerEvents-5.2.1-patch.html
>> - changes naively marked with [ED]. Compare with current
>> https://dvcs.w3.org/hg/pointerevents/raw-file/tip/
>> pointerEvents.html#list-of-pointer-events
>>
>
> An alternative, if this is felt to add too much verbosity and repetition
> to the table, would be to completely remove the mouse compatibility info
> from the table itself, and instead move the problem completely to the
> actual mouse compat section itself (only saying something in a note after
> the table along lines of "If the pointer is primary, most of these events
> will also fire mouse compatibility events. See ... for more details").
>
> I'll tackle that part - including simple examples - in the coming days as
> well. Let me know though what we do with this though...
>
>
> P
> --
> Patrick H. Lauke
> ______________________________________________________________
> re·dux (adj.): brought back; returned. used postpositively
> [latin : re-, re- + dux, leader; see duke.]
>
> www.splintered.co.uk | www.photographia.co.uk
> http://redux.deviantart.com | http://flickr.com/photos/redux/
> ______________________________________________________________
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
> ______________________________________________________________
>
>
Received on Tuesday, 21 January 2014 16:39:27 UTC

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