Fixed
Status Update
No update yet.
Comments
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.
ap...@google.com
Hi!
What is 'partially' exactly?
How do I see it?
Thanks!
What is 'partially' exactly?
How do I see it?
Thanks!
jb...@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
Description
Having just a
remember { }around calls togetBackStackEntry(route)causes new entries with the same id to use the old remember scope which can cause crashes. We should instead be telling devs to useremember(entry) { }using the entry from thecomposablefunction lambda scope as the input to theremembercalculation. This way, whenever the entry object changes, we also recompose therememberand we never get a stale entry.