9615624fc1
The attached bug resulted from a regression in m98 via this change: https://chromium-review.googlesource.com/c/chromium/src/+/3263318 which actually reveals an existing issue with RenderAccessibilityImpl::MarkWebAXObjectDirty. It never passes the correct ax::mojom::EventFrom field from the AXEvent in a higher call in the callstack. Furthermore, in ChromeVox js, we had a codepath in RangeAutomationHandler which never checked the types of actions to allow unconditionally. This series of conditions caused the regression in m98. R=akihiroota@chromium.org Fixed: b/213036939 Test: cq Change-Id: I443dcd251b3ca9d99b5d561eca7b2a60ba8593a2 AX-Relnotes: n/a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3413435 Reviewed-by: Akihiro Ota <akihiroota@chromium.org> Reviewed-by: Nektarios Paisios <nektar@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: danakj chromium <danakj@chromium.org> Commit-Queue: David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/main@{#965735}