GitLab

When an accessibility text or value changed event is raise, assistive software, such as
VoiceOver and ChromeVox, doesn't really know how the previous text was modified.
The event doesn't specify for example if:
a character has been typed, a new line inserted,
a piece of text has been cut, something was pasted, or
the current selection replaced with a new piece of text.
Assistive software, such as screen readers, need to either monitor key presses, or rely on heuristics to determine what to announce.

This patch adds such information to text and value changed events
through a list of event intents which describe the command that was carried out.

R=dmazzoni@chromium.org, yosin@chromium.org

AX-Relnotes: n/a
Bug: 989156
Change-Id: Ie33cfd73d195086c80883315ee8fef13bdff251e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2214951
Commit-Queue: Nektarios Paisios <nektar@chromium.org>
Auto-Submit: Nektarios Paisios <nektar@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#803823}