| a0926f64b419cfd95b7d092f7bd6bee818ccc7e1 |
|
14-Mar-2016 |
George Mount <mount@google.com> |
Fix transition tests execution on older android versions
Bug 27162448
Change-Id: I79de6fd97c2e18f9f05bfc23a8f1f58518182a67
/frameworks/support/v4/tests/java/android/support/v4/app/test/FragmentTestActivity.java
|
| c077b4cd990a9f220a27ad5eca04828e17136064 |
|
14-Jan-2016 |
Adam Powell <adamp@google.com> |
Permit setRetainInstance(true) on nested fragments
Save arbitrarily nested fragments across config changes as
nonconfiguration objects. This permits the use of retain-instance
child fragments as arbitrary opaque dependencies within other
fragments.
Change-Id: Id4f216bdc2ccbfba6410661626329f07b5015349
/frameworks/support/v4/tests/java/android/support/v4/app/test/FragmentTestActivity.java
|
| a76a4339be2f27431a167381187c3f0b0d08f1b7 |
|
29-Jan-2016 |
Daniel Resnick <danielresnick@google.com> |
Allow onActivityResult(...) to be dispatched to nested Fragments.
This fixes https://code.google.com/p/android/issues/detail?id=40537
by allowing onActivityResult(...) calls to be dispatched to the
correct Fragment even if it is nested in another Fragment.
Change-Id: I4b80c2eb1a83de93b95cb26feca5052aa55c9961
/frameworks/support/v4/tests/java/android/support/v4/app/test/FragmentTestActivity.java
|
| 2913b112d6089ea3e7ebe4a807394dd99f3ebc0f |
|
12-Jan-2016 |
Adam Powell <adamp@google.com> |
Eagerly update fragment state when moving between states
Previously we would not set a fragment's new state until the move to a
new target state was fully complete. This causes problems when other
parts of the fragment manager infrastructure (such as lazily
initializing a child fragment manager) read that state while we're
dispatching a state change call to a fragment.
In this situation, adding a child fragment and then calling
executePendingTransactions on the child FragmentManager would not have
the intended effect, as the child FragmentManager would still be in
state INITIALIZING. The expected lifecycle callbacks to the child
fragment would then occur later.
Fix this by updating the fragment state as we go through each phase of
moveToState before we dispatch to the associated onState method,
matching our usual pattern of invoking onFoo methods after foo has
occurred. Delete the redundant resumed field as we now can use the
state directly.
Bug 25019275
Change-Id: Ia637c4d67f3752e8dd591ed9a53a783690e41d80
(cherry picked from commit 20735a45289fdad3d5d31228992e0dccd3d5dd4f)
/frameworks/support/v4/tests/java/android/support/v4/app/test/FragmentTestActivity.java
|
| a1f95ec10cc7e88dcc1c57c92ac5d0c37c2d9553 |
|
01-Dec-2015 |
George Mount <mount@google.com> |
Add test for Fragment Transition.
Bug 25375640
Bug 23688972
Change-Id: If2843092f40bb6cd59894868ef6bb86cdc3efeb9
/frameworks/support/v4/tests/java/android/support/v4/app/test/FragmentTestActivity.java
|