Previously, disabling the consuming logic was
done based on whether we target R.
But this:
- didn't work for Q apps that already use the new API
- causes a bit of unnecessary behavior churn
- requires special-casing the IME
Instead, we look at whether the app has requested to
handle insets with the R setDecorFitsSystemWindows API.
Fixes: 152384150
Test: atest DecorInsetSdk29Tests DecorInsetTests
Change-Id: I754851d0c11dccd21c2fa011cfdc3f0d7396cf60
System apps and the system_server receive async tag checks, while all other
app processes have it disabled. Developers may enable async tag checks
per application with:
$ adb shell am compat 135772972 <app.name>
Bug: 135772972
Change-Id: I154623941eec8e79af347453fbca1b062346c85b
Merged-In: I154623941eec8e79af347453fbca1b062346c85b
Check that the kernel supports the Tagged Pointers feature before asking
libc to disable/enable pointer tagging.
Bug: 153114333
Test: Build coral, note no messages from SetHeapTaggingLevel.
Test: atest CtsTaggingHostTestCases
Change-Id: Id5fbd731aa70f7b0a75525387479f6123628a012
Merged-In: Id5fbd731aa70f7b0a75525387479f6123628a012
Especially with images this was leading to really bad transitions
since the image would pop over immediately.
We now update the counter once the expansion has finished
Fixes: 153392205
Test: add conversations with messages with unread count and image, click on it.
Change-Id: I2ad2ec6a989a21154e3edbf09aabc6d17ea75bd7
Previously we were showing image messages of all senders instead
of just the last one.
This is now fixed.
Fixes: 153388613
Change-Id: I4e9c563c28291de25bf3dbd0ad72940ab59cad6f
Text toasts don't currently support multi-user. This CL prepares toasts
for multi-user by wiring the user information from who requested the
toast (in the form of uid) to ToastUI, where text toasts are actually
rendered.
We go only as far as obtaining a new user-specific context for that user
and using that to construct the view. Actual support will come in future
CLs.
Bug: 151414297
Test: atest android.widget.cts29.ToastTest android.widget.cts.ToastTest
ToastWindowTest ToastUITest NotificationManagerServiceTest
LegacyToastTest
Change-Id: I8c92453c6a2b73c31f9a41ca9ff463d194d4f44f
Target is not populated for "Open With" processed by ChooserActivity.
Adding a null catch in the logger to return default intent.
Bug: 153335691
Test: manual testing and running ChooserActivityTests
Change-Id: Ib7477a9030d0244d33d74690c6aab8b03b88e1e3
Previously we would autolaunch in this case, as
getResolversForIntentAsUserInternal didn't return any apps for
the work profile when it's off. This change adds the
MATCH_DIRECT_BOOT_AWARE and MATCH_DIRECT_BOOT_UNAWARE
flags to the PackageManager#queryIntentActivitiesAsUser call.
Test: manual
Test: atest ResolverActivityTest
Test: atest ChooserActivityTest
Fixes: 153338971
Change-Id: Iedf10d54953b94393c78d6357ce7e5216f3ba261
Previously the expand button layout was always at 80dp which
made the collapsed size increase. we now measure it at
match_parent instead and just internally use another layout
to position it properly.
Fixes: 153204251
Test: add heads up notification, observe normal padding
Change-Id: I76df6529c1a24808bce54ed0d04230cddf7a0c8c
AlertDialog.Builder's setTitle() does not set the title of its
window, which TalkBack uses for announcements.
Make the behavior consistent between the AlertDialog.Builder's
setTitle and AlertDialog's setTitle, which does change the window
title.
Bug: 149755168
Test: Menu titles appear in the node tree debug info and are announced.
by TalkBack. App version info in Settings is announced.
Change-Id: I49deb98ad294538864e413c6c486b4148e06a2b6
Add a Logger for sharesheet and add calls into ChooserActivity.java
Bug: 147508495
Test: manual testing and added unit tests into ChooserActivityTests.
Change-Id: I0024b5020f47475a28c4745af4d8ef268e5f85be
This is a follow up CL to our previous CL [1], which implemented
fail-fast mode for blocking InputConnection APIs based on
IInputMethod.unbindInput() async signal from IMMS to IMS.
What was not implemented in the previous CL was a mechanism to
immediately unblock a sync InputConnection API call that is already
requested to the IME client process and waiting for its response.
With this CL, any blocking InputConnection API fails immediately when
IInputMethod#onUnbindInput() is delivered to the IME process, without
waiting for the full time-out period (MAX_WAIT_TIME_MILLIS == 2 sec)
to pass.
Implementation Note:
The key idea is to use CountDownLatch to compose multiple wait
conditions.composed wait condition. The CountDownLatch is initialized
with 1 then will be decremented when:
A. received a result from the IME client
B. received IInputMethod.unbindInput()
Hence InputConnectionWrapper can simply wait for the CountDownLatch to
become 0 with an existing timeout (MAX_WAIT_TIME_MILLIS) then returns
failure unless the CountDownLatch became 0 because of A.
[1]: I0f816c6ca4c5c0664962432b913f074605fedd27
1d113d041f
Fix: 36897707
Test: atest InputConnectionBlockingMethodTest
Test: InputConnectionBlockingMethodTest#*FailFastAfterUnbindInput()
take shorter time to complete.
Test: Monitor logcat with `adb logcat -s InputConnectionWrapper:*`
while running `atest InputConnectionBlockingMethodTest`
Change-Id: Ic65a95eb5d0fd56f505a02fd9083bcf6694b6734
In aosp, split divider can be snapped to the specific targets
(first, middle, or last)
new concept is freely snapping between non-dismiss targets.
Test: manual test
1. change config_dockedStackDividerFreeSnapMode true in config.xml
2. build
3. make split state
4. drag divider any position
Bug: 123693029
Change-Id: I9fc42fb698659608de6509acc9ad44874e793fd5
