diff options
| author | Svet Ganov <svetoslavganov@google.com> | 2014-08-05 08:41:08 -0700 |
|---|---|---|
| committer | Svetoslav Ganov <svetoslavganov@google.com> | 2014-08-05 16:02:21 +0000 |
| commit | c946f14a67f36d398f30040976ec6e7baf2643ac (patch) | |
| tree | 16232c6c8130e8b1984dad88ed6ed14e92750057 /docs/html/sdk/api_diff/21/changes | |
| parent | ae9251262a99b0927c9b0f1fa9438b00989402f4 (diff) | |
Properly update accessibility manager state.
Applciations that fire accessibility events have to first check
it accessibility is on and then fire the event. If the app fires
an event when the feature is off an exception is thrown. However,
due to the way accessibility state is pushed to the local
accessibility manager it was possible that the app checks that
aaccessibility is off, fires an event, then the state of the
local manager changes by the time the event is propagated up
the view tree and an exception is thrown. This is a regression.
We really want this exception to prevent apps sending events
across processes if accessibility is off, so now the state
we get from the system manager service is applied via a
message so if the app checks that accessibility is off, then
it will remain off (locally) until the event is propagated.
bug:16672964
Change-Id: Icf5d1b1bdff87b58f285f0d9e1a098552513bbe8
Diffstat (limited to 'docs/html/sdk/api_diff/21/changes')
0 files changed, 0 insertions, 0 deletions