Re: Phasing out mouse compatibility events on tap?

On 18/01/2015 05:36, Sangwhan Moon wrote:

> I'm with Olli on this one. Also, with some browsers implementing the
> changed model and some not (I can't see Safari or Presto changing at
> this point), I can't see how this would make life significantly easier
> for content authors.

I admit that even I can only see a marginal advantage here, particularly 
as to solve "double click handling" authors will still need the "this 
event is a compat event / the result of a touch event" API discussed 
separately, so they'll still need to modify their code regardless (at 
which point they can add a "is this a derived event" check to their 
mouse* handler functions too - unless we ARE saying that's a performance 
hit).

Not trolling, but wondering: with regards to Presto, are there any 
browsers on touch devices still using Presto? Old Android devices not 
capable of upgrading to Chromium-based Opera? (I'm guessing older 
desktop installations, as well as TVs and STBs, but these don't have 
touch events, so would be unaffected by this proposed change)

As for Safari, I'm working on the assumption that Apple - since they 
steadfastly refuse to consider Pointer Events - have tacitly / 
off-the-record agreed to try and make Touch Events environment more 
powerful instead by implementing (or at least considering) these sorts 
of changes...(or rather, that the chances are much greater for them to 
implement an extension to TE rather than PE).

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 Sunday, 18 January 2015 09:59:22 UTC