[Webkit-unassigned] [Bug 75506] Improve touch handling performance by reusing the hitTest result

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=75506





--- Comment #4 from Min Qin <qinmin at chromium.org>  2012-01-04 14:14:48 PST ---
>From the spec: https://dvcs.w3.org/hg/webevents/raw-file/tip/touchevents.html
5.6 The touchmove event
The target of this event must be the same Element on which the touch point started when it was first placed on the surface, even if the touch point has since moved outside the interactive area of the target element.

(In reply to comment #3)
> Yes, this is the case. TouchTarget should not change before finger is released. In the current EventHandler.cc, for example, the touchTarget  for TouchRelease and TouchMove is always the node given by TouchPressed.
> Yes, the touchTarget could be removed during touch moves. But since it is ref counted, so as long as eventHandler maintains a pointer to it, it will not be GCed. And subsequent events send to it should do nothing. 
> 
> (In reply to comment #2)
> > > For TouchRelease and TouchMove events, the touchTarget is always the same as the TouchPressed event.
> > 
> > Is it really the case? Page content may move, so another element will be at the touch position. The original element may even be removed already.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.