Fixed
Status Update
Comments
au...@google.com <au...@google.com>
il...@google.com <il...@google.com>
il...@google.com <il...@google.com>
ap...@google.com <ap...@google.com> #3
Project: platform/frameworks/support
Branch: androidx-master-dev
commit d933bd113831acf7ffaccb303a0b1e24461e3a63
Author: Ian Lake <ilake@google.com>
Date: Thu Nov 29 20:56:52 2018
Correct setRetainInstance() docs
Remove comment about retained Fragments
not being supported on the back stack since
that is indeed supported and has been
for some time.
Test: n/a
BUG: 37069045
Change-Id: Ic3c095c2678b25eac6b561d0145f89c69e18be46
M fragment/src/main/java/androidx/fragment/app/Fragment.java
https://android-review.googlesource.com/837642
https://goto.google.com/android-sha1/d933bd113831acf7ffaccb303a0b1e24461e3a63
Branch: androidx-master-dev
commit d933bd113831acf7ffaccb303a0b1e24461e3a63
Author: Ian Lake <ilake@google.com>
Date: Thu Nov 29 20:56:52 2018
Correct setRetainInstance() docs
Remove comment about retained Fragments
not being supported on the back stack since
that is indeed supported and has been
for some time.
Test: n/a
BUG: 37069045
Change-Id: Ic3c095c2678b25eac6b561d0145f89c69e18be46
M fragment/src/main/java/androidx/fragment/app/Fragment.java
il...@google.com <il...@google.com> #4
Took a few years, but this has been fixed for AndroidX Fragments. (Framework fragments are deprecated and Support Library Fragments have been completely replaced with AndroidX Fragments)
Description
The part in the linked documentation where it says "This can only be used with fragments not in the back stack" looks like a it is based on legacy limitations.
I have tested it, and it works perfectly fine with addToBackStack(). According to
I think a lot of people are mislead by this particular piece of documentation, can it be removed?