Fixed
Status Update
Comments
il...@google.com <il...@google.com> #2
Yes, I think we can limit this exception to only cases where you've added a class
or android:name
to automatically inflate a Fragment into your FragmentContainerView
(that still requires the custom layout inflater that FragmentActivity
uses).
That way it will work fine in non-FragmentActivity
cases where you're just using as a container for manually added Fragments.
pa...@gmail.com <pa...@gmail.com> #3
That would be great!
ap...@google.com <ap...@google.com> #4
Project: platform/frameworks/support
Branch: androidx-master-dev
commit 728527e886caa90a6addefc0e337aae203575ce1
Author: Jeremy Woods <jbwoods@google.com>
Date: Fri Nov 20 10:37:25 2020
Only require Activities for inflated FragmentContainerViews
We currently throw an error when attempting to inflate a
FragmentContainerView outside of a FragmentActivity. This requirement is
actually only for views that are being inflated.
This change makes it so we only throw the error for inflated
FragmentContainerViews.
RelNote: "FragmentContainerViews that are not inflated using a class or android:name attribute can now be used outside of a FragmentActivity"
Test: all tests pass
Bug: 172266337
Change-Id: Id4397edf815e6603016e0a7798232c8e9f9f065f
M fragment/fragment/src/androidTest/java/androidx/fragment/app/FragmentContainerViewTest.kt
M fragment/fragment/src/main/java/androidx/fragment/app/FragmentContainerView.java
https://android-review.googlesource.com/1507682
Branch: androidx-master-dev
commit 728527e886caa90a6addefc0e337aae203575ce1
Author: Jeremy Woods <jbwoods@google.com>
Date: Fri Nov 20 10:37:25 2020
Only require Activities for inflated FragmentContainerViews
We currently throw an error when attempting to inflate a
FragmentContainerView outside of a FragmentActivity. This requirement is
actually only for views that are being inflated.
This change makes it so we only throw the error for inflated
FragmentContainerViews.
RelNote: "FragmentContainerViews that are not inflated using a class or android:name attribute can now be used outside of a FragmentActivity"
Test: all tests pass
Bug: 172266337
Change-Id: Id4397edf815e6603016e0a7798232c8e9f9f065f
M fragment/fragment/src/androidTest/java/androidx/fragment/app/FragmentContainerViewTest.kt
M fragment/fragment/src/main/java/androidx/fragment/app/FragmentContainerView.java
jb...@google.com <jb...@google.com> #5
This has been fixed internally and will be available in the Fragment 1.3.0-beta02
release.
Description
Component used: Fragment Version used: 1.3.0-beta01
With lib Fragment version 1.2 it is now recommended to use FragmentContainerView instead FrameLayout but that requires FragmentActivity.
Not sure why this requirement was introduced? In our use case user can use app on phone or mirror app to remote device with means DisplayManager.createVirtualDisplay . In both cases we use same stack of fragments, there is no need to run activity in second flow.
Can we bring this functionality back?