Fixed
Status Update
Comments
il...@google.com <il...@google.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.
ev...@gmail.com <ev...@gmail.com> #3
Hi!
What is 'partially' exactly?
How do I see it?
Thanks!
What is 'partially' exactly?
How do I see it?
Thanks!
il...@google.com <il...@google.com>
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
ev...@gmail.com <ev...@gmail.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
Version used:2.0.0
Devices/Android versions reproduced on:Emulator 8.0, Pixel 2 XL 9.x
So basically for reproduce you need simple flow:
1. Graph with Fragment with arguments with default values as default destination
2. Main Activity launcher which hosts the graph
3. in Activity.onCreate() start listen for destination changes:
navController.addOnDestinationChangedListener { controller, destination, arguments -> }
4. When activity first creates onDestinationChanged() gets called but arguments is null.
Fragment will receive those default arguments tho.
This happens only if fragment is startDestination. If we navigate to this fragment otherwise (clicks, menus) with NavController.navigate() default arguments will be at place.