arc-a11y: Fix wrong focus restore
CL:2398438 changed the focus handling in ARC++ accessibility and when a user visits various windows in the same task, it intended to remember the last focused node for each window. However, there is a bug. ArcAccessiblityHelperService allocates chrome node id to each node and window, and that id is different if the root window id is different. As Android accessibility framework exposes only visible windows, even in the same task, the same chrome node id can be reused because visible root window can easily changes in a task. Thus, we should not have used chrome id to remember the last focused node, instead, we should use the android side window id. This change fixes the above issue. AX-Relnotes: n/a. Bug: b:169201305 (Initial focus issue in TextEditActivity) Test: tast arc.AccessiblityEvent (without CL:2467224) Test: unit_test AXTreeSourceArcTest Change-Id: If55058d9d66a636d54b73d3cd92a4bd2b5fea214 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2467738Reviewed-by:David Tseng <dtseng@chromium.org> Commit-Queue: Hiroki Sato <hirokisato@chromium.org> Cr-Commit-Position: refs/heads/master@{#816850}
Showing
Please register or sign in to comment