summaryrefslogtreecommitdiffstats
path: root/src/plugins/platforms/bsdfb/main.cpp
diff options
context:
space:
mode:
authorTimon Sassor <[email protected]>2025-09-15 13:32:26 +0200
committerLars Schmertmann <[email protected]>2025-10-28 17:35:21 +0000
commit249cec4c5c6a438b8a201b14157f38a3f7a3fad2 (patch)
tree0f24b8906b791222352280382cd6984150afe7c3 /src/plugins/platforms/bsdfb/main.cpp
parent5882310d5d54f897b933044c1447b4b9dee78437 (diff)
Android: Fix double emission of certain a11y eventsHEADdev
3c709198838866d5122c69a30cacdc806605d0cf and e7a211d702d6aa21a30eff56ceeffc153385443e introduced a11y actions for focusing and scrolling. However they also accidentally introduced a double emission of their according events. This causes problems, since every new event stops the processing and announcement of the previous in TalkBack. We remove the sendEventForVirtualViewId() calls from performAction() and performActionForVirtualViewId(), because they are the culprit. If an action like focus or scroll changes the app state, an a11y update is triggered, which ends up calling notifyObjectFocus() or notifyScrolledEvent() where the according event is then emitted and the a11y delegate state is updated. For the focus there is an exception, since an element cannot gain the active focus if is is disabled. However TalkBack should still be able to place its focus frame on that element and read out its content. Pick-to: 6.10 6.8 Change-Id: I9061eec713fd5382feb7aacafdffe393968ef8f1 Reviewed-by: Lars Schmertmann <[email protected]> Reviewed-by: Morten Johan Sørvig <[email protected]> Reviewed-by: Assam Boudjelthia <[email protected]>
Diffstat (limited to 'src/plugins/platforms/bsdfb/main.cpp')
0 files changed, 0 insertions, 0 deletions