The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ac87a1f26b6c2dbf65e11cf9da3ef203763fd87f

commit ac87a1f26b6c2dbf65e11cf9da3ef203763fd87f
Author: dtseng <dtseng@chromium.org>
Date: Wed Jun 21 17:48:44 2017

Don't process text changes when ChromeVox range is elsewhere

BUG= 734816 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2945103002
Cr-Commit-Position: refs/heads/master@{#481239}

[modify] https://crrev.com/ac87a1f26b6c2dbf65e11cf9da3ef203763fd87f/chrome/browser/resources/chromeos/chromevox/cvox2/background/desktop_automation_handler.js

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/84236eb3f0122c8c120d034d9e691be60d1de413

commit 84236eb3f0122c8c120d034d9e691be60d1de413
Author: dtseng <dtseng@chromium.org>
Date: Thu Jun 29 00:51:38 2017

Fix touch typing

Focus can remain on the address bar while ChromeVox range is over the keyboard. When typing occurs, text changes occur in the text field. We should output these events. This should be the only case where ChromeVox responds to text change events that are not in its current range.

BUG= 734816 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2960283002
Cr-Commit-Position: refs/heads/master@{#483233}

[modify] https://crrev.com/84236eb3f0122c8c120d034d9e691be60d1de413/chrome/browser/resources/chromeos/chromevox/cvox2/background/desktop_automation_handler.js