Fixed
Status Update
Comments
il...@google.com <il...@google.com>
jo...@jmb.dev <jo...@jmb.dev> #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!
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
jb...@google.com <jb...@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
an...@google.com <an...@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
Version used: 2.2.0-rc04
Devices/Android versions reproduced on: potentially all
This is kind of a followup to
There seems to be a bug related to the changes introduced in the aforementioned ticket. If I define a simple deeplink like so:
<deepLink
android:id="@+id/deepLinkToSomething"
app:uri="myapp://open/something />
... the deeplink will NOT be executed when I attempt to open an Intent which has the data URI myapp://open/something?someParameter=parameter. The solution to the aforementioned ticket should have made this work by ignoring undefined parameters.
My current local solution (as outlined per
<deepLink
android:id="@+id/deepLinkToSomething"
app:uri="myapp://open/something?dummy={dummy} />
Then it works just fine.
I suspect it has something to do with how the pattern is compiled in the constructor of NavDeepLink in case there are no parameters.