- From: Rick Byers via GitHub <sysbot+gh@w3.org>
- Date: Mon, 25 Jul 2016 14:26:37 +0000
- To: public-pointer-events@w3.org
For reference this automatic capturing behavior is defined for **iOS** [here](https://developer.apple.com/library/ios/documentation/EventHandling/Conceptual/EventHandlingiPhoneOS/event_delivery_responder_chain/event_delivery_responder_chain.html), 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 [here](https://newcircle.com/s/post/1567/mastering_the_android_touch_system). 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 in [ViewGroup.dispatchTouchEvent](https://github.com/android/platform_frameworks_base/blob/4535e11fb7010f2b104d3f8b3954407b9f330e0f/core/java/android/view/ViewGroup.java#L2077). [UIScrollView takes advantage of intercepting](https://github.com/android/platform_frameworks_base/blob/4535e11fb7010f2b104d3f8b3954407b9f330e0f/core/java/android/widget/ScrollView.java#L488) 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 https://github.com/w3c/pointerevents/issues/8#issuecomment-234968602 using your GitHub account
Received on Monday, 25 July 2016 14:26:45 UTC