Previously, there was only a way to inject input after syncing inputs.
However, some tests require a direct call to sync inputs since we need
to ensure the info was propagated to InputManager native before
continuing with the test. This exposes a method just to
syncInputTransactions.
Bug: 130695122
Test: ActivityLifecycleTopResumedStateTests
Test: MultiDisplayPolicyTests
Change-Id: Ie3115741a20d04c743fd854ac421dc3705332488
As of today we register Ime consumer in IMM onWindowGainedFocus().
However, it does nothing functionally when ViewRootImpl#sNewInsetsMode is disabled.
This CL adds a check to not register consumer at the first place.
This may also be causing a leak. Added a TODO to revisit that before we
enable the flag.
Bug: 131181940
Test: atest ViewRootImpl
Test: atest InsetsController
Change-Id: I6b2b62d10670d63edafeb1b24c25b26c7721f3ad
In order to dismiss dialog in accessibility, we would also send
ACTION_OUTSIDE while performing ACTION_CLICK. However, the result
of performing ACTION_CLICK in AccessibilityInteractionClient may
be overwritten by the result of performing ACTION_OUTSIDE. This
causes that TouchExplorer may get incorrect result and follow-up
behavior is different.
Bug: 127902192
Test: a11y CTS & unit tests
Test: After enabling Talkback, manually test on 'View Terms' page
in ManagedProvisioning to check if the section heading can
be expanded/collapsed by double tap.
Change-Id: Id6b1f63ea87418c66bf1aebdea829f656581e8ed
When running cancel animation for drag shadow image, the system cannot
start another drag operation, which is problematic when the system would
start the other drag operation quickly.
Bug: 130313958
Test: Cancel drag operation by calling cancelDragAndDrop
Change-Id: I5d6650a0ce9a4cd80bbdb1beabc9e514349ccadc
A follow up change of ag/7058048.
Also fixed a wrong nullability annotation, ConversationActions.getHints
should be @NonNull.
Bug: 129344540
Test: atest cts/tests/tests/view/src/android/view/textclassifier/cts/
Change-Id: Iae734b4b27dd3dd8294684330bec198072693a57
variants
Updated various framework Views to have equivalent BlendMode APIs
to replace the deprecated PorterDuff equivalents.
Updated InspectableProperty annotations to refer to the same
xml attributes as the original tintmode APIs
Bug: 126726419
Test: Added CTS tests to verify new BlendMode APIs
Change-Id: Id9ab36d3d4d29f351250723e9d13d49bc6062c83
Merged-In: Id9ab36d3d4d29f351250723e9d13d49bc6062c83
This reverts commit 44f5215ee8.
Reason for revert: <Make Ime test in SystemDecorationTest failed>
Bug: 130715649
Change-Id: I9afb1d5ee7e7a4f1e7de6fa4c7c3ec5dcc336f08
Property methods to get/set gesture exclusion rects for a window.
This is useful for games or other frameworks that use Window#takeSurface
and do not have a view hierarchy, leaving the associated View methods
unavailable.
Bug: 130572780
Test: cts via "atest SystemGestureExclusionRectsTest"
Change-Id: I2704aef1d1950158fcabf7c91413bedee08b8971
Also removed ContentCaptureClient, which is not used anymore (it probably became obsolete with the
ContentCaptureOptions optimization).
Fixes: 130585342
Test: atest CtsAutoFillServiceTestCases:android.autofillservice.cts.augmented.AugmentedLoginNotImportantForAutofillActivityTest
Test: manual verification with Dialer app
Change-Id: I041922874fac749f1f5d49793f1ad3e26cc345d6
As per the suggestion from API council, we now have a subclass for event
of each category.
Bug: 129344540
Test: atest frameworks/base/core/tests/coretests/src/android/view/textclassifier/
Test: atest cts/tests/tests/view/src/android/view/textclassifier/cts/
Test: atest frameworks/base/packages/ExtServices/tests/src/android/ext/services/notification/SmartActionsHelperTest.java
Change-Id: Ic43b33c2176447c40e64bd0e410e906d5fb9c4cc
All requests / result objects from TextClassifier have get/setRequest,
so ConversationActions.Request should have them as well.
BUG: 130529981
Test: atest cts/tests/tests/view/src/android/view/textclassifier/cts/ConversationActionsTest.java
Change-Id: I19719b009d4f34df8650c669cc24cb304293407a
To fix the issue that mContext is not updated when moved to another
display, we previously introduce mDisplayContext as a workaround in [1].
Change to use Context#updateDisplay(int) to unify mDisplayContext to
mContext.
[1]: Ifa0ca24e9cf764caf492ee065606680b6a06751a
Bug: 116349163
Test: atest ActivityManagerMultiDisplayTests
Test: atest CtsInputMethodTestCases CtsInputMethodServiceHostTestCases
Test: atest InputMethodManagerTest
Test: atest InsetsControllerTest
Test: atest InsetsSourceConsumerTest
Test: atest ImeInsetsSourceConsumerTest
Test: atest CtsActivityManagerDeviceTestCases:MultiDisplayClientTests
Change-Id: Ic2010e8b533caf01418e0deb8062b8ff597c5abc
Forgot to add this in generateLinks.
BUG: 129119759
Test: frameworks/base/core/tests/coretests/src/android/view/textclassifier/
Change-Id: I1882ed496b4a8aa04aaced4e9d632b47393dccbf
Modify the document of this method, View#setScreenReaderFocusable,
To make as clear and precise as possible
Bug: 109898645
Test: Java Doc Build PASS
Change-Id: I683d420b6f1a4743d57dad9d06a343b85ec5da00
ImeInsetsSourceConsumer was not unregistered when focus lost, it
was still references by InputMethodManager. So, the last activity
in the process won’t be GCed even though it has been destroyed.
Bug: 130216346
Test: atest ImeInsetsSourceConsumerTest
Change-Id: Ida19411d8361180692e7de7e012d2cd3b431fa9f
