- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Fri, 05 Dec 2014 14:59:21 +0000
- To: Arthur Barstow <art.barstow@gmail.com>, Rick Byers <rbyers@google.com>
- CC: "public-touchevents@w3.org" <public-touchevents@w3.org>
On 05/12/2014 14:46, Arthur Barstow wrote: > Wondering aloud here ... do you (or others) have input for such a > document? If so, perhaps it would be helpful to reference a (wiki) > document this CG, PFWG (and others) could create and maintain. I'm trying to understand first of all what the original purpose of the intended document was/is? Anything beyond "these touch events generate these compat mouse events"? because for, say, keyboard events, i know of no implementation that does anything like generate a keypress/keyup/keydown as a result of a touch event. On the other hand, some platforms (e.g. iOS with an attached keyboard and VoiceOver running, or android with a paired mouse) will "fake" touch events at OS level (so it's the OS itself that maps mouse as if it was a finger, from what I can see on Android - and on iOS, it's VoiceOver that's doing it OS-wide), so nothing really that concerns actual browser implementation I think. P -- Patrick H. Lauke www.splintered.co.uk | https://github.com/patrickhlauke http://flickr.com/photos/redux/ | http://redux.deviantart.com twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Friday, 5 December 2014 14:59:44 UTC