Allow startDestination route to use default values [354046047]

Fixed

Feature Request

Status Update

No update yet.

Description

cl...@google.com

created issue #1

Jul 18, 2024 11:16PM

In aosp/2978197, we added a fix so that navigation would parse and store arg values passed through the startDestination route. However, this behavior change is not ideal for existing implementations that rely on the ignored args to fallback to default values.

We should add a user path that will allow them to use default values.

Comments

cl...@google.com <cl...@google.com> #2Jul 19, 2024 12:33AM

Marked as fixed.

Nested scrolling works partially (as per

http://b/122818889). Let's discuss if we need full support and if so make sure it works.

Message last modified on Jul 22, 2024 05:02PM

ap...@google.com <ap...@google.com> #3Jul 19, 2024 12:36AM

Hi!

What is 'partially' exactly?
How do I see it?
Thanks!

pr...@google.com <pr...@google.com> #4Aug 13, 2024 06:58PM

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

Issue 354046047

Description

Issue summary

Comments

cl...@google.com <cl...@google.com> #2Jul 19, 2024 12:33AM

ap...@google.com <ap...@google.com> #3Jul 19, 2024 12:36AM

pr...@google.com <pr...@google.com> #4Aug 13, 2024 06:58PM

Add comment

Issue metadata