We have found that UIGestureRecognizer was not correctly filtering touchesEnded events before passing them on to UIViews it was anchored on (fixed in #305). We now cover the behaviour of touchedMoved and touchesEnded in our tests. It would be good to investigate the behaviour of touchesBegan, as there's a strong suspicion it's not yet being handled correctly.
Possible first steps: compare behaviour with iOS, see how existing TouchHandlingTests, try writing a failing test for it and finding a fix.
Quick note about this from #305:
From memory, touchesBegan works slightly differently on iOS. If the gesture recogniser fails or doesn't exist then (and only then) will touchesBegan be called.
We have found that
UIGestureRecognizer
was not correctly filteringtouchesEnded
events before passing them on toUIViews
it was anchored on (fixed in #305). We now cover the behaviour oftouchedMoved
andtouchesEnded
in our tests. It would be good to investigate the behaviour oftouchesBegan
, as there's a strong suspicion it's not yet being handled correctly.Possible first steps: compare behaviour with iOS, see how existing
TouchHandlingTests
, try writing a failing test for it and finding a fix.Quick note about this from #305: