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: Olli Pettay <Olli.Pettay@helsinki.fi>
Date: Tue, 15 Feb 2011 22:16:41 +0200
Message-ID: <4D5ADF29.9090009@helsinki.fi>
To: Peter-Paul Koch <pp.koch@gmail.com>
CC: Web Events Working Group WG <public-webevents@w3.org>
On 02/15/2011 10:04 PM, Peter-Paul Koch wrote:
>> 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.
Why? Mouse events have element as the target.


-Olli
Received on Tuesday, 15 February 2011 20:17:16 GMT

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