| fed04169c31e7e3d8c7a328876358dd3564062bb |
|
14-Apr-2016 |
Clara Bayarri <clarabayarri@google.com> |
Provide startIntentSenderForResult for fragments
Bug: 27700608
Change-Id: I43139604b0aa60c2dcce93db92a38e1327566a4e
/frameworks/support/v4/java/android/support/v4/app/FragmentHostCallback.java
|
| b054427688e7cf0475bec09da9a3fb7688881459 |
|
15-Apr-2016 |
Adam Powell <adamp@google.com> |
Retain loaders through stopped config changes
Previously we would throw away any stopped LoaderManagers when we went
to retain instances to pass along as nonConfigurationInstances during
config changes or similar activity restarts. This causes loaders to do
more work than they need to when a calling activity starts a new
activity on top, a config change happens (e.g. screen rotation) and
then the top activity is finished, restarting the caller in a new
configuration. The loaders would go through onReset unnecessarily,
potentially throwing away data to be reloaded again after the config
change completes.
Instead of throwing away stopped LoaderManagers in this case, restart
them and retain them across the config change so they can resume where
they left off.
Bug 27176186
Change-Id: I6b589776fd19e0b88a1a00f6763fe8ea6d60db58
/frameworks/support/v4/java/android/support/v4/app/FragmentHostCallback.java
|
| 0e35b9f59703416786e7ac460726c2c06a9194fc |
|
09-Jan-2016 |
Daniel Resnick <danielresnick@google.com> |
Support launching activities with animations from Fragment.
Change-Id: I03eb17d2385fad9e5bfda76889316b5407d7dede
/frameworks/support/v4/java/android/support/v4/app/FragmentHostCallback.java
|
| 64ece2df3d6d789f7a642692acbe85fa1b998d6b |
|
20-Oct-2015 |
Todd Kennedy <toddke@google.com> |
Retain fragment loaders
Remove the partial fix [it did not work for child fragment managers]
and replace with a more general fix that works with all fragments.
Bug: 23838271
Change-Id: Idf7decd64e344013df63359edd2d4268645eb99c
/frameworks/support/v4/java/android/support/v4/app/FragmentHostCallback.java
|
| e1e957f536c20ebe2a7e6c417ccb2fd8f7fa845b |
|
11-Jun-2015 |
Svetoslav <svetoslavganov@google.com> |
Add v4 support for permission APIs on fragments
Change-Id: I5a4abba0f65f5f92632c0031b0f7c259d5c61024
/frameworks/support/v4/java/android/support/v4/app/FragmentHostCallback.java
|
| 4f08e623f23cbb89881f35d3472b78d388b76dc9 |
|
08-Jun-2015 |
Todd Kennedy <toddke@google.com> |
make onGetHost() public
bug: 21698586
Change-Id: Ibe3aec760d20b787c4536b9fbbb00e8d36064244
/frameworks/support/v4/java/android/support/v4/app/FragmentHostCallback.java
|
| 8cbf484d41c18aa4e79f27a26ded0d275171f0dc |
|
04-Jun-2015 |
Adam Powell <adamp@google.com> |
Don't call onAttach twice on v4 fragments
Remove an additional call to Fragment#onAttach in
FragmentHostCallback#onAttachFragment to re-sync with the current
state of the framework FragmentManager.
Bug 20559493
Change-Id: I4e879931b8035c05019cf6d53b14e1c4f12e21f6
/frameworks/support/v4/java/android/support/v4/app/FragmentHostCallback.java
|
| b979cb86fa389effb7cd79fa045550c10b7b4819 |
|
04-May-2015 |
Todd Kennedy <toddke@google.com> |
Call Activity#onAttachFragment()
This was accidentally removed during the changes to abstract a Fragment host.
Bug: 20825263
Change-Id: Ib345606f8ba41ca5b1a1d3b3e6fa47d256fbb90b
/frameworks/support/v4/java/android/support/v4/app/FragmentHostCallback.java
|
| 8491eb62f621cd5de4b4caed839be09c77011f53 |
|
30-Apr-2015 |
Todd Kennedy <toddke@google.com> |
Sync API with platform
While going through the main platform review, there were several
changes to class and method names. Apply those changes to the
support library to maintain parity with the platform.
Bug: 19569096
Change-Id: Ibe36a664c40379665e3482f792220d975974abca
/frameworks/support/v4/java/android/support/v4/app/FragmentHostCallback.java
|