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

Project: platform/frameworks/support
Branch: androidx-main

commit c2365dcfeb9064814282304f30f3eb86be71fdc7
Author: Dan Nizri <dniz@google.com>
Date: Wed Dec 20 16:33:08 2023

Fix Popup back handling on Android T/13+ when android:enableOnBackInvokedCallback="true"

Bug: 313702338
Bug: 318537200
Test: tested with android:enableOnBackInvokedCallback="true"
Change-Id: I7c7cef686ed9fbfd2d144c90040b13528f1675ed

M compose/ui/ui/src/androidMain/kotlin/androidx/compose/ui/window/AndroidPopup.android.kt

https://android-review.googlesource.com/2886766

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

Marked as fixed.

Is there remaining work for this feature request. Support for predictive back in Dialogs would allow Material3 to remove some Dialog forks and would be very helpful!

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