Enable chrome.automation.getDesktop on all aura platforms.

chrome/browser/resources/chromeos/chromevox/cvox2/background/background_test.extjs

 // Copyright 2014 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // Include test fixture.
 GEN_INCLUDE(['../../testing/chromevox_next_e2e_test_base.js']);
 
 GEN_INCLUDE(['../../testing/mock_tts.js']);
 
 /**
@@ skipping 51 matching lines @@
 SYNC_TEST_F('BackgroundTest', 'ClassicNamespaces', function() {
   assertEquals('object', typeof(cvox));
   assertEquals('function', typeof(cvox.ChromeVoxBackground));
 });
 
 /** Tests that ChromeVox next is in this context. */
 SYNC_TEST_F('BackgroundTest', 'NextNamespaces', function() {
   assertEquals('function', typeof(Background));
 });
 
-/** Tests that ChromeVox reads the desktop tree. */
-TEST_F('BackgroundTest', 'DesktopFocus', function() {

[dmazzoni, 2015/03/26 18:44:58]

Why are we losing this test?

[David Tseng, 2015/03/26 23:20:47]

The initial desktop tree is just the root. Until an event gets fired on
something like focus on the status tray, that's all we get. Once focus fires,
the serializer walks up to the window causing the AXAuraObjCache to cache that
window and then, find on an automation node will reach the status tray.

If you know how to focus the status tray from js, we could do that.

[dmazzoni, 2015/03/26 23:32:04]

I know we can't iterate over all windows easily, but I wonder if we could do
something in C++ code when the desktop tree is first requested, like fire an
accessibility focus event on the currently focused view?

What do you think about disabling this test for now rather than deleting it? I
really would like to see tests for things like the status tray one way or
another.

[David Tseng, 2015/03/27 17:04:38]

How about if we add a helper binding that can focus the status tray? I'm not
sure if it helps to keep a disabled test around though as long as we file a bug
for this.

I like the focus idea, but I don't think that would help in this case because we
need to have more native code mixed in among the js calls. This framework
doesn't really allow for that.

-  function findStatusTray(root) {
-    if (root.role == chrome.automation.RoleType.button &&
-        root.attributes.name &&
-        root.attributes.name.indexOf('Status tray') != -1) {
-      return root;
-    }
-    for (var i = 0; i < root.children.length; i++) {
-      var found = findStatusTray(root.children[i]);
-      if (found)
-        return found;
-    }
-    return null;
-  }
-
-  chrome.automation.getDesktop(this.newCallback(function(root) {
-    var testButton = findStatusTray(root);
-    cvox.ChromeVox.tts.expectSpeech('Status tray', this.newCallback());
-    testButton.focus();
-  }));
-});
-
 /** Tests feedback once a page loads. */
 TEST_F('BackgroundTest', 'MANUAL_InitialFeedback', function() {
   cvox.ChromeVox.tts.expectSpeech('start', this.newCallback());
 
   this.runWithTab(function() {/*!
     <p>start
     <p>end
   */});
 });
 
@@ skipping 72 matching lines @@
 TEST_F('BackgroundTest', 'MANUAL_ContinuousRead', function() {
   this.runWithLoadedTree(this.linksAndHeadingsDoc, function() {
     cvox.ChromeVox.tts.expectSpeech('start');
     cvox.ChromeVox.tts.expectSpeechAfter('start', this.doCmd('continuousRead'));
     cvox.ChromeVox.tts.expectSpeech('alpha Link');
     cvox.ChromeVox.tts.expectSpeech('beta Link');
     cvox.ChromeVox.tts.expectSpeech('Heading charlie', function() {});
     cvox.ChromeVox.tts.finishExpectations(this.newCallback());
   });
 });