03a53d1c77
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 |
||
|---|---|---|
| .. | ||
| IInputFlinger.h | ||
| Input.h | ||
| InputDevice.h | ||
| InputEventLabels.h | ||
| InputTransport.h | ||
| KeyCharacterMap.h | ||
| KeyLayoutMap.h | ||
| Keyboard.h | ||
| VelocityControl.h | ||
| VelocityTracker.h | ||
| VirtualKeyMap.h | ||