GitLab

On trunk, we currently fire (infer) a focus event when the focused node changes.

For events originating from Blink, it is not reliable to infer focus events because |event_from| cannot be properly associated with the generated or inferred event or even the set of node updates.

This issue only comes up when repeated accessibility actions are performed, quickly.

The change will fix firing of some focus events that contain the wrong event from value. The user visible change is that ChromeVox will not sync focus (thinking it is not a focus triggered from its own action).

Change-Id: I9926e1d0a03f8a70011c7d38d709eb1c77baee26
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1640141
Commit-Queue: David Tseng <dtseng@chromium.org>
Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#665585}