commit | 74e9c5f21c148a8c68372c1fae290cd733dd0f46 | [log] [tgz] |
---|---|---|
author | Melba Nuzen <[email protected]> | Mon Nov 07 16:29:00 2022 -0800 |
committer | Melba Nuzen <[email protected]> | Tue Feb 07 23:17:35 2023 +0000 |
tree | 4f13b445c038f16182748f22d01541b58532e513 | |
parent | 7ec6f6a5601dce12f0a143c8018a54209f892fb9 [diff] |
Refactor semantics traversal order for more accurate top bars This change uses 1) the idea of structural significance to determine groups of nodes to visit at a time and 2) row groupings to have more accurate traversal order. For each node examined, if it is structurally significant, then all of its children must be placed in the final order list before moving on; if the node is not, then all of its children and its children’s children are extracted, then compared with the grouping algorithm. A structurally significant node for now is determined by if it is a container (Surface), scrollable, or a collection. This fix is mainly focused on addressing top bar ordering issues. The tests added primarily focus on different types of top bars (TopAppBars, Scaffold top bars, top bars with scrolling columns, etc.). New tests were added to `AndroidAccessibilityTest` instead of `SemanticsTests` since the new traversal order is set via ANI properties and needs the ANI provider to test. In addition to those changes, we no longer need semantic node’s `replacedChildrenSortedByBounds` since all previous sorting has been replaced, so that function, the `sortByBounds` parameter, and the `SemanticsSort` file has been removed. Tests in `SemanticsTests` that were related to ordering (tests that started with `testChildrenSortedByBounds`) were removed, but new tests with the same coverage were added to `AndroidAccessibilityTest` in their place. See go/focus-order-changes for more details. Test: compose/ui/AndroidAccessibilityTest/testCreateAccessibilityNodeInfo_forTraversalOrder_SimpleTopAppBar and others Fix: b/264431330 Change-Id: I419ae4feec1b319786a6cc32c883d92cb8bac466
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.