Avoid reconstructing handler when it is already available #5591
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Change
The root cause of this bugs is this seemly harmless call to
AlertRequestHelper.PageIsInThisContext
accidentally disposed theGestureManager
through this stack.When the GestureManager is disposed of, the associated
OnTouchListener
is unregistered. Later on, it will register theOnTouchListener
for a label again. But that label is not the same instance as the one that is currently showing, that is why touching the label for the second time won't lead to the event listener.My observation is that all this heavy lifting just to check if the page is in the current activity is a lot of waste. We could have just reused the existing Handler instance, that is what inspired the fix.
Issues Fixed
Fixes #5425