Fixed
Status Update
Comments
il...@google.com <il...@google.com>
fo...@google.com <fo...@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.
il...@google.com <il...@google.com> #3
Hi!
What is 'partially' exactly?
How do I see it?
Thanks!
What is 'partially' exactly?
How do I see it?
Thanks!
fo...@google.com <fo...@google.com>
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
cl...@google.com <cl...@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
Component used: Compose Navigation Version used: 2.5.1 Devices/Android versions reproduced on:
Issue Description
I added Deeplink support for json files to one of my Compose Screens like this
After opening a json file the app navigates to the correct screen, but when the user clicks on the toolbar back button and navigateUp is triggered the app crashes instantly with following stacktrace:
After adding a default argument to the nav composable the app doesn't crash, but it feels like a dirty workaround because the argument is never actively used.
Is it possible to read the file uri from an argument? if yes, how does the deeplink and the argument need to be declared?
Sample Project:https://github.com/TobyEb/NavigationFileDeeplink