Avoid touch lockup due to mQuickReturn == true #587
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.
This can happen when a DOWN event is triggered in the quickreturn area, and the finger then moved out of that area without triggering a drag (e.g. by moving vertically first and then across). If the menu is then closed in some other way (e.g. back key) the CustomViewAbove remains in mQuickReturn == true state and blocks all touches to the main content, making the app appear unresponsive or crashed to the user.