| f31c0a3f96f3a18d623b9161a18faede3ddc8413 |
|
04-Apr-2016 |
George Mount <mount@google.com> |
Merge "Restore fragment transaction animation state information." into mnc-ub-dev
am: 57056fe
* commit '57056fe597b941347185fd4849c05796c2b29daa':
Restore fragment transaction animation state information.
Change-Id: I9acbb49f37dab39246f932373e4c5481dcb335f6
|
| 2a34327ae05fe323476f4bf40be5de6eebd59cbe |
|
30-Mar-2016 |
George Mount <mount@google.com> |
Restore fragment transaction animation state information.
Bug 17487986
Change-Id: I11c5f5742c54e0630a83f7e23da4777fddd2bcba
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| 59b0cd6a6455f4ba8dda349364de518df4da49f2 |
|
01-Mar-2016 |
George Mount <mount@google.com> |
Merge "Ensure that fragments are created in added order." into nyc-dev
|
| 36bd1e9880a74cc53edef99040bbb24fc1cad909 |
|
24-Feb-2016 |
Adam Powell <adamp@google.com> |
Protect FragmentManager against View.NO_ID container ids
Not all code paths for FragmentManager were checking that the
container view had a valid view id. As we can't correctly restore a
fragment with a container without one, throw a more descriptive
exception earlier.
Update the FragmentPagerAdapter implementations to be even more
descriptive if the host ViewPager does not have a view id and we would
enter this case.
Bug 27290033
Change-Id: I3e349ceaa82fbbd1f257554d9670e4c21f49ff4e
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| a674400277f88005ad43df76e42a18fcc067102e |
|
16-Feb-2016 |
George Mount <mount@google.com> |
Ensure that fragments are created in added order.
Bug 26894030
Change-Id: I8e477038547f5a1a0edefb34737a1759db5676fa
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| e1fad6fb0ee83d7f2dad3ec3dca6641a425e7244 |
|
13-Jan-2016 |
Adam Powell <adamp@google.com> |
FragmentTransaction.commitNow
Offer commitNow and commitNowAllowingStateLoss methods on Fragment for
use by encapsulated components using fragments as implementation
details. This can help prevent unexpected ordering side effects at the
app level when a call to a library method wants to commit and
immediately initialize a fragment as an implementation detail.
Note that this change still does not permit reentrant FragmentManager
operations. It is still an error to add/remove/change fragments in the
same FragmentManager while a fragment transaction is being executed.
Have the commonly used ViewPager adapters use commitNow instead of
executePendingTransactions.
Change-Id: I386333899cf96c2496b084480d61063b857d8f43
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| 776e65a4d65f7e1aa050f6666a98c2089ed79676 |
|
06-Jan-2016 |
Aurimas Liutikas <aurimas@google.com> |
Merge "Change fragment removal order for fragment replacement." into mnc-ub-dev am: 8b01e78a92
am: 533325dae1
* commit '533325dae1d86fd35f357e11c48254ebd7a14ee6':
Change fragment removal order for fragment replacement.
|
| c5cea33d2092d265a2b0806ca94400dc85ab5499 |
|
05-Jan-2016 |
Aurimas Liutikas <aurimas@google.com> |
Change fragment removal order for fragment replacement.
Before this patch it for loop was accessing mManager.mAdded elements using
an integer index and also removing the fragments from mAdded using
mManager.removeFragment().
Bug: 24693644
Change-Id: I20828ce83c8d22aad6ae7ce3dfe88dd3d7aa4e01
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| b672771ab4758258c22c547b55e8d17039c3f61b |
|
04-Dec-2015 |
George Mount <mount@google.com> |
Merge "Revert "Revert "Choose the correct Fragment to pull a Transiton from.""" into mnc-ub-dev am: aa63f0a7d3
am: 8992f8da54
* commit '8992f8da5493cb0a8e39b9a005b3b3b480e219c9':
Revert "Revert "Choose the correct Fragment to pull a Transiton from.""
|
| 3d069d50f59ab74b62e41db13e852577fcb0052b |
|
04-Dec-2015 |
George Mount <mount@google.com> |
Revert "Revert "Give transitioning fragment a context prior to retrieving transition"" am: bc1f5ea21c
am: 0654e2413c
* commit '0654e2413c405ac5f0523a2457edfc21d0fc323a':
Revert "Revert "Give transitioning fragment a context prior to retrieving transition""
|
| aa63f0a7d3d57fc26f15b20a76f066c894a8d39b |
|
04-Dec-2015 |
George Mount <mount@google.com> |
Merge "Revert "Revert "Choose the correct Fragment to pull a Transiton from.""" into mnc-ub-dev
|
| c062f4fc524e635888fe2c0de1325f6f6b6137bf |
|
04-Dec-2015 |
George Mount <mount@google.com> |
Revert "Revert "Choose the correct Fragment to pull a Transiton from.""
This reverts commit f24dfa0a078af3ccefda7c23b5addf781f6c6d77.
Change-Id: I917b5c50cef16be546c308eca97ed671df0881e5
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| bc1f5ea21c2f5f887cb77c2b965c4d5fa7b46ea2 |
|
04-Dec-2015 |
George Mount <mount@google.com> |
Revert "Revert "Give transitioning fragment a context prior to retrieving transition""
This reverts commit 54e009bfbee9e76bed06a16d70c080d19f7757fb.
Change-Id: I3f1c967b4a511d09e9b665d9234f1b88ec8fd00b
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| d43174ae8a4e5c9852ff38f8edde91fb9631909d |
|
03-Dec-2015 |
George Mount <mount@google.com> |
Merge "Revert "Give transitioning fragment a context prior to retrieving transition"" into mnc-ub-dev am: bc276be458
am: 041739528c
* commit '041739528c2f683816631201b99c48862bb4f68b':
Revert "Give transitioning fragment a context prior to retrieving transition"
|
| 55ce43d1a435f22eb08c908839d74d681c158f30 |
|
03-Dec-2015 |
George Mount <mount@google.com> |
Merge "Revert "Choose the correct Fragment to pull a Transiton from."" into mnc-ub-dev am: f845344a9a
am: d0ec1b3f46
* commit 'd0ec1b3f463020e0d303561360a3b7777e4f7631':
Revert "Choose the correct Fragment to pull a Transiton from."
|
| f845344a9a020a2413d7a03c024d1918564332f4 |
|
03-Dec-2015 |
George Mount <mount@google.com> |
Merge "Revert "Choose the correct Fragment to pull a Transiton from."" into mnc-ub-dev
|
| f24dfa0a078af3ccefda7c23b5addf781f6c6d77 |
|
03-Dec-2015 |
George Mount <mount@google.com> |
Revert "Choose the correct Fragment to pull a Transiton from."
This reverts commit 82297fddbc3c11e290f21b207d64ab8a56b63510.
Change-Id: Iae4ab7e020abf07c9efb68454029534e549393b0
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| 54e009bfbee9e76bed06a16d70c080d19f7757fb |
|
03-Dec-2015 |
George Mount <mount@google.com> |
Revert "Give transitioning fragment a context prior to retrieving transition"
This reverts commit b7c2b7dc5ae729d62d313dce364335dba06c61d0.
Change-Id: I14d84090a837a04f6ae5e13874b881eb46b5bff3
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| f7d49a83d586d03facf7d2dcefc9b97f2146aa98 |
|
02-Dec-2015 |
George Mount <mount@google.com> |
Merge "Choose the correct Fragment to pull a Transiton from." into mnc-ub-dev am: 5b6741adc5
am: 5c1b2e78ed
* commit '5c1b2e78ed637bb049f96acb7191c93a890d8888':
Choose the correct Fragment to pull a Transiton from.
|
| aaf633f1fb33dc98342a3de247d1da9961bdb000 |
|
02-Dec-2015 |
George Mount <mount@google.com> |
Merge "Give transitioning fragment a context prior to retrieving transition" into mnc-ub-dev am: a797f3ff7d
am: 40f332b0e0
* commit '40f332b0e097c6e1ffd711c8b32e61704c6257ff':
Give transitioning fragment a context prior to retrieving transition
|
| 5b6741adc5271a623e598f6af0cefeceb8189820 |
|
02-Dec-2015 |
George Mount <mount@google.com> |
Merge "Choose the correct Fragment to pull a Transiton from." into mnc-ub-dev
|
| 82297fddbc3c11e290f21b207d64ab8a56b63510 |
|
01-Dec-2015 |
George Mount <mount@google.com> |
Choose the correct Fragment to pull a Transiton from.
Bug 25375640
When popping multiple back stacks or replacing multiple times
within a transaction, the wrong fragment could have been
chosen. This normally occured when one of the Fragments had
a null Transition.
Change-Id: Ifaca5fa0262706e83056f1f4afbab2154238f241
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| b7c2b7dc5ae729d62d313dce364335dba06c61d0 |
|
30-Nov-2015 |
George Mount <mount@google.com> |
Give transitioning fragment a context prior to retrieving transition
Bug 23688972
An incoming fragment that is going to execute a transition may
need to have a context in order to load the transition. This
CL moves the state of incoming fragments to CREATED prior to
getting their Transitions.
Change-Id: Ic066fae24273309f1cadeadc13ed92bb30bbbaa6
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| ee22cd83dc6c6f65f93a91713452cbd5a8a12a51 |
|
09-Sep-2015 |
George Mount <mount@google.com> |
Ensure entering and exiting views don't match in Fragment Transitions.
Bug 23693301
An enter or exit transition targeting an ID, name, or similar
would match by the given criteria. This disreguarded that the
exiting view should not match against the entering views, even
if they have the matching criteria.
This excludes the exiting and shared elements from participating in
the enter transition and the enter and shared elements from
participating in the exit transition.
Change-Id: Id57f23434cd8c95cba8ea1483cceafac21d3762f
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| 05a2eeb7e0ac538747c1233b80ca0f9088ea033a |
|
30-Jun-2015 |
George Mount <mount@google.com> |
Merge "Fix FragmentTransaction replace() behavior" into mnc-dev
|
| 1727b768eeeaa246791db74db868574049a562c4 |
|
29-Jun-2014 |
Eddie Ringle <eddie.ringle@gmail.com> |
Fix FragmentTransaction replace() behavior
Bug 22174959
According to FragmentTransaction's reference, replace()
should be equivalent to remove()'ing every fragment in
a given container and then adding the specified fragment
to replace those that were removed.
Commit 5506618c80a292ac275d8b0c1046b446c7f58836 broke
this intended behavior in the support library.
This patch makes it so that the removal loop doesn't
end prematurely. It also fixes an issue where the
replace operation would remove fragments regardless
of their container after encountering the first fragment
with a matching container ID.
Relevant issues:
http://b.android.com/43265
http://b.android.com/52112
http://b.android.com/53393
http://b.android.com/68856
http://b.android.com/70803
Change-Id: Ieab4468fa7a2afb63bd5fd87a21bbd95d54d638f
Signed-off-by: Eddie Ringle <eddie.ringle@gmail.com>
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| e1eea177bd4993151679183e88171f1e50c33054 |
|
25-Jun-2015 |
George Mount <mount@google.com> |
Fixed bug preventing shared elements from transitioning.
The wrong collection was passed, never allowing shared elements
to be targeted.
Change-Id: If23fdcfc80a3c4a30dc4062a8c2ecc38bb43f5c3
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| c33885b865c99ce9ae96214f0e9d7bd1ca12cb93 |
|
15-Jun-2015 |
George Mount <mount@google.com> |
Limit shared element transition to shared elements and children.
Bug 20257189
Shared element transitions should target the shared elements
or their children. When no target is given to a transition,
the transition should target the shared element. If a target
is given, it should also be able to target the children of
the shared element.
This is solved by wrapping the shared element transition
with a TransitionSet. The set is given the targets of all
shared elements and their children. Further, if no target
is given for a transition, the transition is given only
the shared elements as targets.
Change-Id: I4c13c849898b89c60d9bc0a8dd34d7c5543f2bdc
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| 5f2544c0082203c392bae9b08401d5d9e73ab94d |
|
04-Jun-2015 |
George Mount <mount@google.com> |
Clean up the enter transition even if there is not entering fragment.
Bug 21618103
Change-Id: Ib63dd282be1a5df3ffff305a7dc95f1c906f52f0
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.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/BackStackRecord.java
|
| 845332cbde9f3624ff4b266e81fb3aae658793ea |
|
10-Apr-2015 |
George Mount <mount@google.com> |
Fix bug in Fragment Transitions where shared elements use same name.
Bug 19641883
Change-Id: I5d5d30f9fa04328347f86f5998222849fa99ecfa
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| d608cf6e08769bf320c1b595cbbd9a7664160449 |
|
26-Mar-2015 |
Todd Kennedy <toddke@google.com> |
Remove dependency upon FragmentActivity
The FragmentManagerImpl is intimately tied with a FragmentActivity. In
many cases, we want to be able to create / manage Fragments outside of
a FragmentManager. This defines a FragmentController interface that can
be used by any class to host Fragments.
Bug: 19569096
Change-Id: I62dee733a70577d0d3c8f96a89e4b05a3d5e18b0
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| 2f0e3626990f52844ec637cb4ffaaa2dee11eb61 |
|
18-Feb-2015 |
George Mount <mount@google.com> |
Protect popFromBackStack with SDK_INT check.
Bug 19229940
Change-Id: I90a2b5e6523761ede62de37a22dbd624274f6bca
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| c766ad5a6e0c115f08b933ede22375c7070a3391 |
|
31-Oct-2014 |
George Mount <mount@google.com> |
Only modify add Transition targets when they aren't targeted.
Bug 18191727
Transitions were targeting specific views, but they do this by
adding targets. If there was already a view targeted, now that
transition also targeted a different view. This prevents that
by only targeting views when no target was given.
Change-Id: I003d531c6d249e5fdec5a544d37220350838bb3a
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| 62260534040eba52462875a435df2c1f50ab846e |
|
19-Sep-2014 |
George Mount <mount@google.com> |
Target only shared elements with shared element Transition
Bug 17549213
Bug 17553253
Change-Id: I82b9f52fdd8b386abd5839e1471fab82f890b327
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| 983592c887664932c3b27433ef9fb1ff191a7972 |
|
19-Sep-2014 |
George Mount <mount@google.com> |
Merge "Fix exception when fragment container has no View." into lmp-dev
|
| 7516316ffdf6fbf7b248c615404831191daa66a4 |
|
18-Sep-2014 |
George Mount <mount@google.com> |
Fix exception when fragment container has no View.
Bug 17535259
Change-Id: Ic58886e93557b8894d4754597889bd29476259de
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| 8dfd79ec7028cfdfa1ba69ed7cbf27aac41dc78a |
|
18-Sep-2014 |
George Mount <mount@google.com> |
Fix custom animations disabled always.
Bug 17549252
Custom animations should only be disabled when fragment transitions
are running.
Change-Id: I8ec0bc9b90ce7d149b1c5fe25363bb5e7bbe315b
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| 5a8f14de0bb4304f9a3aebdcb35ee0dd607f27f7 |
|
15-Sep-2014 |
George Mount <mount@google.com> |
Fixed enter/exit transitions working against shared elements.
Bug 17499971
The enter and exit transitions were targeting the shared element.
This means you'd get double transitions on the shared element.
Fixed bug where the wrong views were targeted when there was
only one enter/exit/shared element transition.
Change-Id: Ieb3a4cfcd35479a82adc3ee269c5b0015ab5d5af
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| 6739bc7f97ba5486b6f6114fb3812b098822cc3c |
|
10-Sep-2014 |
George Mount <mount@google.com> |
Merge "Move capturing entering views until just before transition." into lmp-dev
|
| 0f5ae57910484f1d873fdad90966b6244a633bd4 |
|
08-Sep-2014 |
George Mount <mount@google.com> |
Move capturing entering views until just before transition.
Bug 17407387
Bug 17420256
Recycler view doesn't instantiate its views until after
the onCreateView call. This delays the capturing of
final views until just before the entering state is
captured for the Transition.
Change-Id: Ifd6ecaa21cefb4f6f8f720b319993bf0b9e2d8f7
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| a52784195525cdb1f2bb4d8dde1b8b314f480957 |
|
10-Sep-2014 |
Chet Haase <chet@google.com> |
Remove references to "L"
Issue #16894783 Remove references to L when API is locked down
Change-Id: Icf1215eed34e6fbe3d71a5cec4bf1699c3bc3ff9
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| 9306f07b1d66f4974a81f781d29739b30124fff0 |
|
29-Aug-2014 |
George Mount <mount@google.com> |
API Review: change SharedElementListener to SharedElementCallback
Bug 17289526
Change-Id: I49f8d838207524fbf0ec099021bcf7312c28bd82
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| 9f4a046cbeb22a24d322a644323b41022ad9d15a |
|
02-Sep-2014 |
George Mount <mount@google.com> |
Change Fragment Transitions to match Activity Transitions API.
Bug 17188255
Change-Id: I99897ba3c78f3f140000a719afbcfac951e43290
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| 128bb5c66d0b34c5a658c682deb3a0b9199b20c4 |
|
22-Aug-2014 |
George Mount <mount@google.com> |
API Review: change fragment transition methods.
Bug 16959326
Change-Id: Ie0aea3b3a6fd432ca061d8bf8a245e0a3ec25e99
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| 4500be62dea3895a98336122a2944cc4ab024bc5 |
|
27-Jun-2014 |
George Mount <mount@google.com> |
Add support for shared elements in fragment transitions.
Bug 15891071
Custom transitions in the Fragment Transaction have a
higher priority than animations, transition style, or
transition resource. If the API < 20, custom transitions
will not be active and the other animation types will
take effect.
Change-Id: I7f18f9b9a75f73d58a16184a301458bdcd331098
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| 3a7571011a8f2c2e2685c4e3e7a6fa46673ee7ea |
|
27-Sep-2012 |
Dianne Hackborn <hackbod@google.com> |
Work on issue #7232641: ISE crash when rotating phone in label list mode
This doesn't fix the problem; I think it is an app problem. It does
improve a bunch of the debugging to help better identify what is going
on, and introduces some checks when adding a fragment to fail
immediately if we are getting into a state when a fragment is going to
be in the added list multiple times (which is pretty much guaranteed
to lead to a failure at some point in the future).
Change-Id: Idac978eb6bd2bd38d54e50532907c40b264ac300
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| 5506618c80a292ac275d8b0c1046b446c7f58836 |
|
05-Jun-2012 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #6584942 IllegalStateException: Failure saving state...
...active SuggestFragment{419494f0} has cleared index: -1
There were issues when the same fragment was removed and then
added again before completely finishing the remove (such as due
to a running animation).
Two fixes:
- Now when you call FragmentTransaction.replace() and are replacing
a fragment with the same fragment, this becomes a no-op, to avoid
visual artifacts in the transition and bad states.
- When we are moving the fragment state up and it is currently
animating away to the INITIALIZED state, we could end up making
the fragment inactive as part of the cleanup. In this case it
shouldn't be made inactive; we just need to initialize it but
keep it active since we are going to continue to use it.
Bug: 6584942
Change-Id: I4c37a8e48b115feb0892ef0eb92316d7aeba7b1b
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| 2a4d8518f36346ea25a22a736453ff28f2954165 |
|
30-Aug-2011 |
Dianne Hackborn <hackbod@google.com> |
Fix issues 5158104 and 4981556 (fragment problems)
5158104: com.android.contacts: java.lang.IllegalStateException:
Can not perform this action after onSaveInstanceState at
android.app.FragmentManagerImpl.checkStateLoss(FragmentManager.java:1201)
The ViewPager can just commit without worrying about a state loss,
since it can correctly reconstruct its state later.
4981556: Fragment.mImmediateActivity doesn't get restored on orientation change
I am giving up on this thing; I just don't see how it can actually
be correct. So now instead of getting an exception about a dup
add/remove at point of the add/remove call, this will happen later when
processing the transaction.
Also add an API for controlling the visibility of menus, which ViewPager
uses to have the correct menus shows. And add a method to get the
name of a back stack entry.
Finally fix a recent problem in ViewPager with dealing with focus,
and make ViewPager smart about handling keyboard focus navigation
inside itself.
Change-Id: I280269ac64079d171e9c899ea1cff7e80246c924
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| df6f1393f73a488ba2661b28d3d88a5ac19c4ea2 |
|
26-Jul-2011 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #5063010: Loaders don't seem to be properly...
...retained with compatibility library
Also we never implemented the full custom animation stuff in the support
lib. Now it is there.
Change-Id: I25b410752fdc3e7ae876802fdc8d7a62e4b07236
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| eedc67283a5a49dce86c625e54596dfdea9465a7 |
|
05-Apr-2011 |
Dianne Hackborn <hackbod@google.com> |
First submit of FragmentPager class.
This provides an easy way to build a UI where the user can
swipe left or right through its elements. The elements are
implemented as fragments, and the class takes care of managing
those fragments as the user navigates through it.
This implementation also introduces a new FragmentManager
concept of a "detached" fragment -- basically a way for you
to put a fragment in the same state as when it is on the
back stack, where the framework is managing its current state
but it is no longer actively running.
Also required the introduction of new compatibility code for
MotionEvent and VelocityTracker for accessing multi-touch data.
Change-Id: I997492cfc6f1969f1a5d775385afb830f5a47795
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| cba2e2c881e8e16ea5025b564c94320174d65f01 |
|
08-Feb-2011 |
Dianne Hackborn <hackbod@google.com> |
First checkin!
Change-Id: Ib09737c48a144dd778efe4750452d74ac8265a29
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|