Bug: 7073422
The feature that is using search box implementation was removed from
browser after Honeycomb. This is to remove the js interface that
is added for this feature.
Clean cherry pick of d773ca8ff2a7a5be94d7f2aaa8ff5ef5dac501a8
Change-Id: I033d29718d08803f375759faf83e2058df6d4906
...to fix background->shutdown delivery race
Add ACTION_STOPPING and ACTION_STARTING to allow such apps to keep track of
which users are started/stopped, and be involved in the process of stopping
a user.
Also get rid of the scale part of the wallpaper transitions, since it seems
like I have still failed at getting the user switch to wait until the new
wallpaper is displayed.
Change-Id: If7e8fdae3544a9d7987a1b9274dc8b49022f6f62
1. We are showing a warning dialog if the user enables an accessibility
service that requests explore by touch. This dialog was shown only
for the owner but should be shown for the current user.
bug:7304437
Change-Id: I692b5112df16405e6d2e4890aafbfde79981f973
The first way I had it produces somewhat unexpected behavior. If you
scroll past the top of the list, focus moves down to the control
below.
This changes it so scrolling past the bottom of the list moves focus
to the next control below.
Change-Id: I886e1854df85ceb203dac61c7f8c7daf6749e90e
The query WindowState.isDisplayed did not take into account being
displayed due to app animations.
When an existing input method target was animating away the logic
for detecting if it was still on screen was faulty. This led to
assigning the input method to a layer below its target and obscuring
the input method until the animation was complete.
Bug: 7296703 fixed.
Change-Id: Ib00db4f21b726ed57d25d6a1e796b65a7d45ee97
When Face Unlock failed the maximum number of times (3), it was asking
for account login when it should have been asking for the backup lock
that the user chose when setting up Face Unlock.
This change splits the isBiometricUnlockEnabled() function into two.
One of them strictly checks whether it exists and is selected. The
other one checks whether too many attempts have occurred. When
deciding which backup to choose, the decision is now based only on
whether Face Unlock is enabled. Checking whether too many attempts
had occurred caused the bug because the check indicated it had already
'fallen back' to pattern, and the backup for pattern was being
selected instead of the backup for biometric unlock.
Change-Id: I6b9cf2c5155e8c14933cbfc8f5d58ebc007e53cb
Make Bitmap.copyPixelsFromBuffer() adjust the buffer's position,
making it consistent with Bitmap.copyPixelsToBuffer().
b/6948775
Change-Id: Ie26f8050b1fb4d19cd39ee1a08b6f652a732fec3
The cling interception code can interfere with the touch
stream to the point that PanelView might get an ACTION_UP or
_CANCEL without a corresponding ACTION_DOWN, causing
problems.
Bug: 7301742
Change-Id: Idd5074c2544b3238517655ab3c068966bae9f912
There was a workaround used in a previous release where we effectively
ignored cancel events to work around another bug. This change removes
the workaround and GlowPadView correctly handles the event.
Bug 6903638
Change-Id: I9b510985c6da346a4e10cf2535267c8d5efa5871
