W3C home > Mailing lists > Public > public-webevents@w3.org > January to March 2011

Re: WebEvents-ISSUE-7: Targets for touch events: Elements or Nodes? [Touch Events spec]

From: Peter-Paul Koch <pp.koch@gmail.com>
Date: Tue, 15 Feb 2011 21:04:15 +0100
Message-ID: <AANLkTikYfmFp_5WSnQu2Y-wbP5mVs6=QneG+U8MRxUY0@mail.gmail.com>
To: Web Events Working Group WG <public-webevents@w3.org>
> http://www.w3.org/2010/webevents/track/issues/7
>
> Raised by: Matt Brubeck
> On product: Touch Events spec
>
> Andrew Grieve <http://lists.w3.org/Archives/Public/public-webevents/2011JanMar/0043.html>:
> [[
> Targets for touch events, Elements or Nodes?
>  -iOS and Android the target will be a #textnode if one was under the tap
>  -mouse events seem to use the parent element of the #textnode as the
> target.
> ]]

This is an ancient bug in WebKit. Very early versions (Safari 1 or
thereabouts) had this problem with pretty much all events. It was
solved later, and frankly I thought it had disappeared entirely.
Apparently not so.

Making a text node the target of an event never makes sense from a web
development perspective. I advise you to always make the correct Node
the target.

-- 
--------------------------------------------
ppk, mobile platform strategist
http://quirksmode.org/about/
+.31.6.29585782
--------------------------------------------
Received on Tuesday, 15 February 2011 20:04:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 15 February 2011 20:04:48 GMT