Accessibility focus should be updated after paint
In crrev.com/c/1930061 the accessibility focus event in TableView was tweaked so that it would always fire after the accessibility information had been updated. However, there are instances when the accessibility information is updated more than one time. We need to fire the focus event after paint, to ensure that the accessibility tree has become stable and won't update right away again. The order of the problematic operations are: 1. The Task Manager refreshes its contents at a constant interval. OnItemsChanged is called which calls SortItemsAndUpdateMapping and which in turn calls UpdateVirtualAccessibilityChildren. This would update the accessibility focus as well. 2. OnPaint is called and in some cases, whenever the contents of the Task Manager are sorted, SortItemsAndUpdateMapping would also be called, which updates the virtual accessibility children a second time without updating the focus, since the focus had already been updated. R=sky@chromium.org, dmazzoni@chromium.org Bug: 811277 Change-Id: Ifbf8a6908f3411030912f30981aa3c22f1874f8e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1946691 Auto-Submit: Nektarios Paisios <nektar@chromium.org> Reviewed-by:Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Nektarios Paisios <nektar@chromium.org> Cr-Commit-Position: refs/heads/master@{#722504}
Showing
Please register or sign in to comment