GitLab

If the Accessibility node becomes undefined during reading, the
default behavior is to stop reading immediately. This allows STS
to continue reading hen nodes are undefined.

Advanced users may want more control over text, while novice users
may be surprised when text continues after windows are closed (and
there's no visual indicator that speech is still in prgoress).

An open question is whether this should also apply to nodes that
disappear from the screen after their window is closed or minimized,
or if they are scrolled off screen. Right now, that behavior is
read and is unchanged by this patch.

Adds this behind the --enable-experimental-accessibility-features
flag in Chrome OS.

Bug: 818835
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: Ib063d6ac5071f35a5d4e0a90cd472bb0ffc165f9
Reviewed-on: https://chromium-review.googlesource.com/949776
Commit-Queue: Katie Dektar <katie@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541617}