History log of /frameworks/native/services/inputflinger/InputWindow.h
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
b9be0cf397eb6053fb5b472d91cf2d6a22c6693f 26-May-2016 Michael Wright <michaelwr@google.com> Mark the multiwindow divider as a trusted overlay.

Having it be untrusted breaks the permissions granting dialog in
multiwindow mode.

Bug: 28828041
Change-Id: I9193dbce7315ebaa205673edd4f406d0b72665c8
/frameworks/native/services/inputflinger/InputWindow.h
cdcd8f2b25a4bf32bb7506fc98ba541d274c9a31 23-Mar-2016 Michael Wright <michaelwr@google.com> Add new MotionEvent flag for partially obscured windows.

Due to more complex window layouts resulting in lots of overlapping
windows, the policy around FLAG_WINDOW_IS_OBSCURED has changed to
only be set when the point at which the window was touched is
obscured. Unfortunately, this doesn't prevent tapjacking attacks that
overlay the dialog's text, making a potentially dangerous operation
seem innocuous. To avoid this on particularly sensitive dialogs,
introduce a new flag that really does tell you when your window is
being even partially overlapped.

We aren't exposing this as API since we plan on making the original
flag more robust. This is really a workaround for system dialogs
since we generally know their layout and screen position, and that
they're unlikely to be overlapped by other applications.

Bug: 26677796
Change-Id: I9e336afe90f262ba22015876769a9c510048fd47
/frameworks/native/services/inputflinger/InputWindow.h
0c17a2b2ea5c7bd4f6c9bd426e67c40022e3d84c 11-Nov-2014 Craig Mautner <cmautner@google.com> Stop consuming input on error dialogs.

This code is no longer necessary and was preventing input from
reaching their desired windows. See bug 17648830.

Change-Id: Ib1c026ece70e6fa98343340b89af4199d6d0ffca
/frameworks/native/services/inputflinger/InputWindow.h
51eb29fa9a2ffe9c5adb9ea25bfbd51992ff16a4 23-Apr-2014 Conley Owens <cco3@android.com> Add TYPE_MAGNIFICATION_OVERLAY to isTrustedOverlay

This fixes a bug where a View with filterTouchesWhenObscured will have
all touches filtered when in magnification accessibility mode. This is
due to magnification being a separate Window over top of the running
Activity. The method onFilterTouchEventForSecurity in View will then
always return false when filterTouchesWhenObscured is enabled on the
View. By adding the magnification Window to the list of Trusted Overlays
we can ensure that touches will work properly with this property
enabled.

This corresponds to AOSP change
I07706588a625682d05da5cb19f401139eb08a54c

Change-Id: Iba095433a1f9045349d1b47a58a33b850ed31c97
/frameworks/native/services/inputflinger/InputWindow.h
d02c5b6aace05d9fd938e2d03705ac4f60f8da19 11-Feb-2014 Michael Wright <michaelwr@google.com> Move inputservice over to frameworks/native

Add all of the underlying input system pieces, minux PointerController and
SpriteController, to inputflinger. This is in preparation for moving input to
its own process and the addition of the input HAL.

Try 2.

Change-Id: I5f571fe86eb570885ae994e1f0552fb558930346
/frameworks/native/services/inputflinger/InputWindow.h
1b1fe314c4e74ef85afe4dacd7ba1e87e6862aa3 11-Feb-2014 Michael Wright <michaelwr@google.com> Revert "Move inputservice over to frameworks/native"

This reverts commit 2dceb67f1f32bd2ec589c4ac3d83da0b8dbe4a5c.
/frameworks/native/services/inputflinger/InputWindow.h
2dceb67f1f32bd2ec589c4ac3d83da0b8dbe4a5c 10-Feb-2014 Michael Wright <michaelwr@google.com> Move inputservice over to frameworks/native

Add all of the underlying input system pieces, minux PointerController and
SpriteController, to inputflinger. This is in preparation for moving input to
its own process and the addition of the input HAL.

Change-Id: I1419a740b38756bd0d54fef5f5ca337e6815b1b0
/frameworks/native/services/inputflinger/InputWindow.h