Re: [pointerevents] Pointermove should not require a hit-test by default for touch

For reference this automatic capturing behavior is defined for **iOS**
 in particular:
> Note: A touch object is associated with its hit-test view for its 
lifetime, even if the touch later moves outside the view.

**Android** is more complex and less well documented. The best 
overview I've been able to find is 
  Basically when the first finger goes down, views can register their 
interest in the touch, including the ability to intercept future 
events (for that finger or additional fingers).  Then movement events 
are sent only to the intercepting view, or views which explicitly 
registered interest (i.e. hit-testing is typically only done of the 
first down).  The most interesting parts of this logic are implemented
  [UIScrollView takes advantage of 
 so that in the common case of scrolling, events are dispatched 
directly to that view.

GitHub Notification of comment by RByers
Please view or discuss this issue at 
using your GitHub account

Received on Monday, 25 July 2016 14:26:45 UTC