Remove the need for a container id in NavHostFragment [139421197]

Fixed

Feature Request

Status Update

No update yet.

Description

jg...@google.com

created issue #1

Aug 14, 2019 05:25PM

Currently `NavHostFragment` requires a container with non-zero id, which prevents it from working with the following `FragmenTransaction` method:
`public FragmentTransaction add(@NonNull Fragment fragment, @Nullable String tag)` -- which is what e.g. `ViewPager2` uses.

See

http://b/133640271 for more information and a sample reproducing the issue.

Comments

il...@google.com <il...@google.com> Aug 19, 2019 10:22PM

Accepted by il...@google.com.

ap...@google.com <ap...@google.com> #2Aug 20, 2019 12:01AM

Submitter:

Can you please provide a brief text explanation of:

What is the summary of the issue you're seeing
What is the expected behavior
What is the actual behavior
What software is showing the bug. What version of software are you reporting it against
What operating system are you running (android version, device)
If an app integration, what version of emojicompat or emoji2 are you linking against.

Thanks!

il...@google.com <il...@google.com> #3Aug 20, 2019 04:33PM

Marked as fixed.

This has been fixed internally and will be available in Navigation 2.2.0-alpha02

Issue 139421197

Description

Issue summary

Comments

il...@google.com <il...@google.com> Aug 19, 2019 10:22PM

ap...@google.com <ap...@google.com> #2Aug 20, 2019 12:01AM

il...@google.com <il...@google.com> #3Aug 20, 2019 04:33PM

Add comment

Issue metadata