commit | 937fa523a427c942b00b9dcb5f056b5d03454160 | [log] [tgz] |
---|---|---|
author | Jeremy Woods <[email protected]> | Wed Jul 20 16:56:50 2022 -0700 |
committer | Jeremy Woods <[email protected]> | Tue Jul 26 16:12:18 2022 -0700 |
tree | e6c6a5a92560444511e3ec970ccbd0785000cdbe | |
parent | 58a3e2b2f83c15ae3b917e2b94ba0a84916eb0f2 [diff] |
Move all Fragment animations in the same direction Say you have 3 fragments, A, B, and C. If you add A and B with one set of entering and exiting animations. And then pop B, before adding C with an different set of entering and exiting animations while using the recommended setReorderingAllowed=true flag on your fragment transactions, it is possible to get in a scenario where the visible exiting fragment, B, uses the animations from the popping opertion to A instead of the adding operation with C. The reason for this is that the animations for B are set during the first operation with the pop from B to A. The system is then techinically doing a replace operation from A to C, since B has already been popped, so it sets the proper animations on A and leaves B untouched. This causes B to run the stale animations from the pop instead of the current animations from the replace. We should ensure that we always run the animations from the operation that determines what will be visible to user on the screen. RelNote: "Fragments will now run the proper animations when mixing pop and replace operations." Test: added FragmentAnimationTest Bug: 214835303 Change-Id: Ib1c07bd0e05c0c1a3d785e29456bad9afb183e2d
Jetpack is a suite of libraries, tools, and guidance to help developers write high-quality apps easier. These components help you follow best practices, free you from writing boilerplate code, and simplify complex tasks, so you can focus on the code you care about.
Jetpack comprises the androidx.*
package libraries, unbundled from the platform APIs. This means that it offers backward compatibility and is updated more frequently than the Android platform, making sure you always have access to the latest and greatest versions of the Jetpack components.
Our official AARs and JARs binaries are distributed through Google Maven.
You can learn more about using it from Android Jetpack landing page.
For contributions via GitHub, see the GitHub Contribution Guide.
Note: The contributions workflow via GitHub is currently experimental - only contributions to the following projects are being accepted at this time:
When contributing to Jetpack, follow the code review etiquette.
We are not currently accepting new modules.
Head over to the onboarding docs to learn more about getting set up and the development workflow!
Our continuous integration system builds all in progress (and potentially unstable) libraries as new changes are merged. You can manually download these AARs and JARs for your experimentation.
Before uploading your first contribution, you will need setup a password and agree to the contribution agreement:
Generate a HTTPS password: https://android-review.googlesource.com/new-password
Agree to the Google Contributor Licenses Agreement: https://android-review.googlesource.com/settings/new-agreement
AndroidX uses git to store all the binary Gradle dependencies. They are stored in prebuilts/androidx/internal
and prebuilts/androidx/external
directories in your checkout. All the dependencies in these directories are also available from google()
, jcenter()
, or mavenCentral()
. We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.