Bug 60896 - PanGestureRecognizer sometimes won't fire completed event when dragging very slowly
Summary: PanGestureRecognizer sometimes won't fire completed event when dragging very ...
Status: RESOLVED DUPLICATE of bug 39768
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.4.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2017-11-28 17:12 UTC by Richard Pike
Modified: 2017-11-28 17:23 UTC (History)
17 users (show)

Tags: ac
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Richard Pike 2017-11-28 17:12:18 UTC
+++ This bug was initially created as a clone of Bug #39768 +++

When panning, sometimes the PanGestureRecognizer won't reach its completed state when dragging very slowly. This is noticeable on at least Android

Project to use, for ease: https://developer.xamarin.com/samples/xamarin-forms/WorkingWithGestures/PanGesture/

To Reproduce:
Add debug logs or breakpoints at the Gesture.Completed case in the PanContainer.cs's OnPanUpdated method.
When running the application, start a pan, hold it for a moment or two, and release.

Expected behavior:
The completed state is reached.

Resulting behavior:
Occasionally/frequently, this state is not reached.
Comment 1 Paul DiPietro [MSFT] 2017-11-28 17:23:38 UTC
Please reopen the initial bug as this makes reports easier to manage.

*** This bug has been marked as a duplicate of bug 39768 ***