Fixed
Status Update
Comments
sh...@gmail.com <sh...@gmail.com> #2
Nested scrolling works partially (as per http://b/122818889 ). Let's discuss if we need full support and if so make sure it works.
il...@google.com <il...@google.com>
jb...@google.com <jb...@google.com> #3
Hi!
What is 'partially' exactly?
How do I see it?
Thanks!
What is 'partially' exactly?
How do I see it?
Thanks!
ap...@google.com <ap...@google.com> #4
As of now:
- Nesting scroll views with a scroll direction perpendicular to the ViewPager2's orientation inside ViewPager2 works
- Nesting scroll views with a scroll direction parallel to the ViewPager2's orientation inside ViewPager2 does not work
- Nesting scroll views with a scroll direction perpendicular to the ViewPager2's orientation inside ViewPager2 works
- Nesting scroll views with a scroll direction parallel to the ViewPager2's orientation inside ViewPager2 does not work
il...@google.com <il...@google.com> #5
Horizontal ViewPager2 not correctly working into a vertical RecyclerView
Set a setNestedScrollingEnabled to the RecyclerView into the ViewPager2 (across reflection) resolves the problem
Set a setNestedScrollingEnabled to the RecyclerView into the ViewPager2 (across reflection) resolves the problem
na...@google.com <na...@google.com> #6
ageevvalentin@gmail.com, could you provide a sample app? I'd like to learn more about the circumstances that cause the problem; putting a clean ViewPager2 inside a clean RecyclerView seems to work fine, so there must be other factors involved.
Description
Steps to reproduce the problem (including sample code if appropriate).
TestBottomNav.zip
to Android Studio and runDashboard
orNotification
item on BottomNavigationView.What happened.
There is no response after clicking tab item, meanwhile there is no related exception messages printed in Logcat.
This abnormal behaviour was intentional made on my part, just to amplify the problem. To fix it, go to
app/src/main/res/menu/bottom_nav_menu.xml
, change everyandroid:id
starts withNavigation
tonavigation
will be fine.NavigationUI
should not ate the exception message with a simplefalse
return. This will drive novice developers crazy to find out the problem. SeeNo.