Bug P2
Status Update
No update yet.
Comments
go...@schildbach.de
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Expected output
What is the expected output?
Current output
What is the current output?
al...@google.com
al...@google.com
ti...@google.com
al...@google.com
How can you possibly need more information, i just told you the exact part of code causing the issue, and the code changes required to fix it!
Please read the description.
Expected output:
What is the expected output?
See attached "expected.webm" video in OP
Current output
What is the current output?
See attached "actual.webm" video in OP
Please read the description.
Expected output:
What is the expected output?
See attached "expected.webm" video in OP
Current output
What is the current output?
See attached "actual.webm" video in OP
al...@google.com
1. Import attached project
2. Install and run on Android 5 (Lollipop) or above
3. Click FAB and see it fall below/behind the navigation bar once the Snackbar disappear
2. Install and run on Android 5 (Lollipop) or above
3. Click FAB and see it fall below/behind the navigation bar once the Snackbar disappear
ad...@google.com
Could you please check the attached project as we couldn't extract the files from it.
Description
Typically, when a fling occurs onStartNestedScroll() is called with type ViewCompat.TYPE_NON_TOUCH and if you return true, after the fling onStopNestedScroll() is called with TYPE_NON_TOUCH.
BUG: If you interrupt the fling, the matching onStopNestedScroll() is never called.
This means you app can behave unexpectedly, including memory leaks etc. depending on your implementations of the callbacks and how much they depend on correctly matching calls of onStart/onStop.