- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Fri, 01 Aug 2014 01:28:09 +0100
- To: public-pointer-events@w3.org, "public-touchevents@w3.org" <public-touchevents@w3.org>
On 31/07/2014 18:38, Jacob Rossi wrote: > Supporting Touch Events is our next step in helping rationalize these > two models together as it gives us the implementation experience to help > contribute to this group with how Pointer and Touch Events coexist, > enables a compatible web experience for our users today, and makes it > smoother for web developers to transition their sites from Touch to Pointer. > > Going forward, we continue to see Pointer Events as the best model for > the web. In the blog post, you’ll see that we did an experiment with > Touch Events on devices that support other input modalities like mouse > and keyboard. What we found was that about 10% of top sites were broken > for mouse/keyboard users due to coding patterns that assume Touch Events > support means touch-only devices (we’ll share the specific site data > once I’ve compiled it in a digestible form). This is one example of why > we’ll continue to encourage developers to use Pointer Events. It’s also > one reason why (for the time being) we intend for Touch Events to be in > IE mobile only. > > If you have questions or concerns, don’t hesitate to ask. Is it too early to ask how, exactly, this will shake out on pages that register handlers for BOTH touch and pointer events? Will PEs take precedence? What about handlers that are added dynamically a lot later than on page load? (And any indication when the update will be pushed out on the 8.1 developer preview channel? And/or would it be possible to send a note to the list when it is out, just so we can start testing things?) 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, 1 August 2014 00:28:34 UTC