Initial support for accessible text fields and focus tracking in ARC++

chrome/browser/resources/chromeos/chromevox/cvox2/background/desktop_automation_handler.js

Index: chrome/browser/resources/chromeos/chromevox/cvox2/background/desktop_automation_handler.js
diff --git a/chrome/browser/resources/chromeos/chromevox/cvox2/background/desktop_automation_handler.js b/chrome/browser/resources/chromeos/chromevox/cvox2/background/desktop_automation_handler.js
index a981fc54ae4aacf0750a6785f8e35bb183143d9c..2d5f7b7da8a02738d3d16830d09f211743605b68 100644
--- a/chrome/browser/resources/chromeos/chromevox/cvox2/background/desktop_automation_handler.js
+++ b/chrome/browser/resources/chromeos/chromevox/cvox2/background/desktop_automation_handler.js
@@ -396,10 +396,14 @@ DesktopAutomationHandler.prototype = {
    */
   onEditableChanged_: function(evt) {
     var topRoot = AutomationUtil.getTopLevelRoot(evt.target);
-    if (!evt.target.state.focused ||
-        (topRoot &&
-            topRoot.parent &&
-            !topRoot.parent.state.focused))
+    if (topRoot && topRoot.parent && !topRoot.parent.state.focused)
+      return;
+
+    // Only process editable text events if either system or ChromeVox focus is

[dmazzoni, 2017/03/17 03:22:37]

I think this might break contenteditable if the selection start and end are both
children of the contenteditable root. Maybe walk up to the focused ancestor or
something?

[David Tseng, 2017/03/17 15:38:32]

Yeah, I think you're right. The issue is that on Android, the text field doesn't
actually get focus as we're currently computing it. I might think about
explicitly tracking focus on the Android end to help us from not doing this.
I'll try to do something there before this change since comparing ranges is
fragile.

+    // on the target.
+    if (!evt.target.state.focused &&
+        (!ChromeVoxState.instance.currentRange ||
+            ChromeVoxState.instance.currentRange.start.node != evt.target))
       return;
 
     if (!ChromeVoxState.instance.currentRange) {