- From: Rick Byers <rbyers@google.com>
- Date: Sat, 1 Feb 2014 18:43:15 -0500
- To: "Patrick H. Lauke" <redux@splintered.co.uk>
- Cc: "public-pointer-events@w3.org" <public-pointer-events@w3.org>
- Message-ID: <CAFUtAY8xFR-x0gs9kL2q3CeZicrHEM9dOGJON5QKddpwDvzKVQ@mail.gmail.com>
I'd be happy to see some note to this effect - it doesn't sounds like it's on the list of things explicitly outside the charter of the group: http://www.w3.org/2012/pointerevents/charter/. But I doubt we want to go into much detail here (probably more the responsibility of the touch events community group). Rick On Thu, Jan 30, 2014 at 7:52 PM, Patrick H. Lauke <redux@splintered.co.uk>wrote: > Just as an initial question: would it be in scope for the pointer events > spec to have an informative note about the relationship of pointer events > and the (reverse engineered) W3C Touch Events spec? In particular, I'm > thinking something to the effect that touch events and pointer events are > different at a fundamental implementation level (e.g. when mouse compat is > dispatched, the fact that touch events treat click as mouse compat, the > implicit vs explicit capture model), and that this spec does not cover how > these different models can be reconciled...and that it's up to UAs to work > this out? > > (partly inspired by https://bugs.webkit.org/show_bug.cgi?id=105463#c33) > > Thoughts? > > 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 Saturday, 1 February 2014 23:44:04 UTC