GitLab

These four events are (1) properly covered by AXEventGenerator,
(2) don't have any very specific logic in ChromeVox, they just
call onEventIfInRange, and (3) they aren't ever fired by views
in a place where AXEventGenerator wouldn't be able to infer the
same event.

For those reasons, these 4 are safe to switch over.

Bug: 699438
Change-Id: I05037a29e63e01b2be1a23c1057750ada24f0172
Reviewed-on: https://chromium-review.googlesource.com/1215058Reviewed-by: David Tseng <dtseng@chromium.org>
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589977}