tree 51ef883fc560ccde47381b14e2f619dd716be7de
parent 013fd2112bb2ffde9b4d6474f5192466cdfa8320
author Amir Hardon <amirh@users.noreply.github.com> 1551738410 -0800
committer GitHub <noreply@github.com> 1551738410 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJcfaYqCRBK7hj4Ov3rIwAAdHIIAJsOvD/8fY3LrtLciZ1oWYDR
 MsCjvX7id4BrKBCboUM6UiYNkDvwaQzUZbsP8J8UmPyey3X16G/VqSrpKrlzfqCN
 A74pWrsMY9L/S+ZFwB/yRuZWd21yZwMbz9938R2hbNgiRCGdU1StadBx7Dh5tbmL
 FI54QAFldWG1Y9m5C5pExrogid0cgyNiI0aF4JZU2+uEuFIlArHJVkIRl2fspdqT
 aBsxN+Nwfp9HGTR9R5gQgP2kTuzI2SlQYtyvJSaVVeDkDQ6joYU4f2fdjcScvkiT
 EvlLQABNsxDjPIcIJ/W8huWejv9OTtIox9JLMcyaJBD5eVLFaeh9CZRXakDQUSA=
 =Tst7
 -----END PGP SIGNATURE-----
 

Make RenderUiKitView reject absorbed touch events (#28666)

When a touch event that is in the bounds of a RenderUiKitView is absorbed by another render object,
the RenderUiKitView's handleEvent is not called for that object. On the platform side, the touch event hits the FlutterTouchInterceptingView which is waiting for a framework decision that never arrived on whether to reject or accept the gesture.

This change fixes the issue by having RenderUiKitView register a global PointerRoute, that is used to reject absorbed touch events.