| commit | 482188b32ced02dd295b04a31f1650b2bba9b02d | [log] [tgz] |
|---|---|---|
| author | Ralston Da Silva <[email protected]> | Wed Jan 11 17:26:56 2023 -0800 |
| committer | Ralston Da Silva <[email protected]> | Tue Jan 31 09:25:07 2023 -0800 |
| tree | 04ca83372bfbead4ec3893e07cef3661c6053d9c | |
| parent | cfd0dbb4a3b0296320995ffa347a3dc2ec821db4 [diff] |
Fix failing input mode related tests on API 34 We currently have two touch mode related changes in API34: 1. Each window gets its own Input Mode, and the unlike previous versions, the default input mode is Keyboard mode and not Touch mode. 2. The touch mode change listener is not called for all windows views, but is only called for views in windows which have focus. The code in compose sets the touchmode during initialization. We now initialize the touch mode during onAttachToWindow. Also, InstrumentationRegistry sets the global touch mode state, and we need to set the touch mode for the window hosting ComposeView. So instead of using InstrumentationRegistry we set the touch mode using The Compose InputManager API. We also observed some flakiness when touch mode was changed, so we now clean up after every test by resetting the touch mode to the default value. Fixes: 262903257 Fixes: 262909049 Fixes: 262329840 Fixes: 262329591 Fixes: 262329583 Bug: 266755180 Bug: 267253920 Test: ./gradlew compose:ui:ui:cC -P android.testInstrumentationRunnerArguments.package=androidx.compose.ui.input.InputModeTest Test: ./gradlew compose:f:f:cC -P android.testInstrumentationRunnerArguments.package=androidx.compose.foundation.ClickableTest Test: ./gradlew compose:f:f:cC -P android.testInstrumentationRunnerArguments.package=androidx.compose.foundation.selection.SelectableTest Test: ./gradlew compose:f:f:cC -P android.testInstrumentationRunnerArguments.package=androidx.compose.foundation.selection.ToggleableTest Change-Id: Ie0984d6373989ae4c92c216200ce5e5d4b3caae0
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.