commit | 4b2ae6c58df5ac91ffc59939650e955e47b97b64 | [log] [tgz] |
---|---|---|
author | sallyyuen <[email protected]> | Wed Mar 25 12:55:13 2020 -0700 |
committer | sallyyuen <[email protected]> | Wed Aug 26 15:40:53 2020 -0700 |
tree | 929cc2031e6414cec4058012a4447d0b5610c3d4 | |
parent | 6adfc05a4fdaf6cc27f33fdf71a3ed03457b3db7 [diff] |
Make panes important for accessibility for <P For <P, views that are set as panes are not automatically considered important for a11y, so WINDOW_STATE_CHANGED events were not being sent to a11y services. To align the <P andP+ behaviors, we explicitly make a pane important here. Major changes: 1) If a pane is not explicitly marked as not important, mark it with YES. For consistency, reflect the isImportantForAccessibility logic in the platform by including the parent check. 2) Avoid redundancy and don't send an event from ViewCompat on P+, since this already occurs from the platform 3) Support sending CONTENT_CHANGE_TYPE_DISAPPEARED events. Relnote: "For pre-P, ensure panes are marked as important for accessibility and support CONTENT_CHANGE_TYPE_PANE_DISAPPEARED events." Bug: 151399296 Test: Manual test on pre-P and post-P devices to check for CONTENT_CHANGE_TYPE_PANE_APPEARED/DISAPPEARED. Added tests in AccessibilityDelegateCompatTest ./gradlew core:core:connectedAndroidTest --info --daemon -Pandroid.testInstrumentationRunnerArguments.class=androidx.core.view.AccessibilityDelegateCompatTest#testAccessibilityPaneTitle_isSentOnAppearance ./gradlew core:core:connectedAndroidTest --info --daemon -Pandroid.testInstrumentationRunnerArguments.class=androidx.core.view.AccessibilityDelegateCompatTest#testAccessibilityPaneTitle_isSentOnDisappearance Change-Id: Iaeffc6991881face6569627c662fe77bfbf289eb
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 Paging, Room and WorkManager are being accepted at this time.
When contributing to Jetpack, follow the code review etiquette.
We are not currently accepting new modules.
NOTE: You will need to use Linux or Mac OS. Building under Windows is not currently supported.
repo
(Repo is a tool that makes it easier to work with Git in the context of Android. For more information about Repo, see the Repo Command Reference)mkdir ~/bin PATH=~/bin:$PATH curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo chmod a+x ~/bin/repo
git config --global user.name "Your Name" git config --global user.email "[email protected]"
mkdir androidx-master-dev cd androidx-master-dev
repo
command to initialize the repository.repo init -u https://android.googlesource.com/platform/manifest -b androidx-master-dev --partial-clone
repo sync -j8 -c
You will use this command to sync your checkout in the future - it’s similar to git fetch
To open the project with the specific version of Android Studio recommended for developing:
cd path/to/checkout/frameworks/support/ ./studiow
and accept the license agreement when prompted. Now you're ready to edit, run, and test!
If you get “Unregistered VCS root detected” click “Add root” to enable git integration for Android Studio.
If you see any warnings (red underlines) run Build > Clean Project
.
You can do most of your work from Android Studio, however you can also build the full AndroidX library from command line:
cd path/to/checkout/frameworks/support/ ./gradlew createArchive
You can build maven artifacts locally, and test them directly in your app:
./gradlew createArchive
And put the following at the top of your ‘repositories’ property in your project build.gradle
file:
maven { url '/path/to/checkout/out/androidx/build/support_repo/' }
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.
Run FooBarTest
Run androidx.foobar
The AndroidX repository has a set of Android applications that exercise AndroidX code. These applications can be useful when you want to debug a real running application, or reproduce a problem interactively, before writing test code.
These applications are named either <libraryname>-integration-tests-testapp
, or support-\*-demos
(e.g. support-v4-demos
or support-leanback-demos
). You can run them by clicking Run > Run ...
and choosing the desired application.
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
cd path/to/checkout/frameworks/support/ repo start my_branch_name . # make needed modifications... git commit -a repo upload --current-branch .
If you see the following prompt, choose always
:
Run hook scripts from https://android.googlesource.com/platform/manifest (yes/always/NO)?
If the upload succeeds, you'll see output like:
remote: remote: New Changes: remote: https://android-review.googlesource.com/c/platform/frameworks/support/+/720062 Further README updates remote:
To edit your change, use git commit --amend
, and re-upload.
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.