| c05ad763e973f347f3220cd40e8b735a85120810 |
|
06-Mar-2017 |
George Mount <mount@google.com> |
resolve merge conflicts of 890378e35d to master
Test: ran fragment tests
Change-Id: I664e6544397d1f242ef14719bb70747aa9ef88b1
|
| 6a5ddc9c208bb615b3397aa8705e3e4ad73c4a62 |
|
03-Mar-2017 |
George Mount <mount@google.com> |
Fix Loader bugs
Bug 32758881
Bug 34264461
When destroying the LoaderManager, the host was not being cleared.
The host was being leaked and this leaked the Activity.
When a LoaderManager is reused, for example with an orientation
change, the host was updated, but it wasn't started. This
adds a test for that case to ensure that when a reused
LoaderManager is loaded that it is properly started.
Test: ran fragment tests
Change-Id: I71fa5e53b20a8e1ff3ff721a954568ffd6a7227e
/frameworks/support/fragment/java/android/support/v4/app/FragmentHostCallback.java
|
| 147dc4013c78a78ff28849f38d1091b300803a21 |
|
12-Feb-2017 |
Christophe Beyls <software@digitalia.be> |
Fixed Fragment's LoaderManagers leaking the previous Activity after configuration change.
Sync the support library's code with the platform's code.
Issue: https://code.google.com/p/android/issues/detail?id=227136
Test: Verified by running manual tests (heap dumps)
Change-Id: I08fdef05295ab75fd284e2c80b7c6df6f572b51c
/frameworks/support/fragment/java/android/support/v4/app/FragmentHostCallback.java
|
| 990e6fc0326f5948736650c0cb71b6002d443c9c |
|
14-Oct-2016 |
George Mount <mount@google.com> |
Add optimize and postpone transactions.
Bug 29631389
Bug 30502032
Bug 20068723
When multiple operations are executed at once, they sometimes
cancel each other. For example, if the following transactions
are queued:
Transaction 1: add A
Transaction 2: replace with B
This can be trimmed down to add B.
This CL optimizes fragments in both add and pop directions.
Developers can choose not to allow optimization by
using FragmentTransaction#setAllowOptimization
Fragments in a transaction can now indicate when they are ready
and the transaction should complete. Postponed transactions will
have new views in the fragments created and added to the hierarchy
INVISIBLE. When all postponed fragments are ready, the transitions
and animations will start. INVISIBLE views will be made VISIBLE
and removed views will be taken out of the View hierarchy
Test: gradlew connectedCheck in fragment/
Test: manual tests also, just to make sure
Change-Id: I3fdab8e75cb33a02e9e636ff6f43a6f95a564d21
/frameworks/support/fragment/java/android/support/v4/app/FragmentHostCallback.java
|
| c9a859537b0871f84afeeb706a5b425fe3f2b4dd |
|
25-May-2016 |
Aurimas Liutikas <aurimas@google.com> |
Fix a random assortment of spelling errors.
Fix spelling errors found by Android Studio.
Change-Id: I121c79029f4e323da4ff2f44891e25480c44ebbc
/frameworks/support/fragment/java/android/support/v4/app/FragmentHostCallback.java
|
| ff22d81f6561f6cdd2a91eb63238c41079927a22 |
|
12-May-2016 |
Kirill Grouchnikov <kirillg@google.com> |
Extracting fragments and widgets into their own modules.
Also rename core to core-utils.
Change-Id: Icef764d01bc49cd4d04ac4ce47faadda983f4c48
/frameworks/support/fragment/java/android/support/v4/app/FragmentHostCallback.java
|