tree 929cc2031e6414cec4058012a4447d0b5610c3d4
parent 6adfc05a4fdaf6cc27f33fdf71a3ed03457b3db7
author sallyyuen <sallyyuen@google.com> 1585166113 -0700
committer sallyyuen <sallyyuen@google.com> 1598481653 -0700

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