Fixed
Status Update
Comments
ap...@google.com <ap...@google.com> #2
It seems that this ordering is caused by FragmentManager's addAddedFragments()
, which is being removed/reworked as part of
No update yet.
It seems that this ordering is caused by FragmentManager's addAddedFragments()
, which is being removed/reworked as part of
Description
Allow developers to detect when they are using a container for their fragments other than the recommended
FragmentContainerView
.This would apply to any Fragment that was added with a
containerViewId
(i.e., via the respective methods onFragmentTransaction
). It would not apply to headless fragments / fragments added without a container ID.