Fixed
Status Update
No update yet.
Comments
cl...@google.com
ap...@google.com
Nested scrolling works partially (as per http://b/122818889 ). Let's discuss if we need full support and if so make sure it works.
cl...@google.com
Hi!
What is 'partially' exactly?
How do I see it?
Thanks!
What is 'partially' exactly?
How do I see it?
Thanks!
na...@google.com
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
zy...@gmail.com
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
Description
Component used: Navigation
Version used: 2.8.5
The
NavDestination.fillInLabelmethodlabelof theNavDestinationwith arguments. However, it does this by (in every case butNavType.ReferenceType) by just callingargs[argName].toString()- e.g., just directly callingtoString()on the object in theSavedStatebundle.While this approach works for simple types, a custom
NavTypemight not store their class directly in the Bundle - for example, if using the@Serializablesupport, it would be stored as aBundle, which means thetoString()is unlikely to actually be what is needed.Instead,
fillInLabelshould take into account theNavTypeand use itsgetmethod to give theNavTypecontrol over exactly the object that is synthesized from the arguments. That way, developers could implement a customtoString()implementation on their object to control how it is displayed in the label.