[orca] Don't use pyatspi to cache children

[Joanmarie Diggs <joanied src gnome org>]

commit 257be208660f1eea4a2ea50393349a0e922f9fbf
Author: Joanmarie Diggs <jdiggs igalia com>
Date:   Tue May 26 14:37:34 2015 -0400

    Don't use pyatspi to cache children
    
    Doing so seems to make us more dependent on app developers to create
    accessible objects in a particular order. If they fail to do so, we
    get an index in parent of -1 which makes the accessible look like a
    candidate Zombie. Not caching children appears to work around this.
    Whether or not it has side effects we don't like remains to be seen.
    Unstable branch is unstable.

 src/orca/scripts/default.py |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)
---
diff --git a/src/orca/scripts/default.py b/src/orca/scripts/default.py
index d5fb732..db8c736 100644
--- a/src/orca/scripts/default.py
+++ b/src/orca/scripts/default.py
@@ -143,7 +143,8 @@ class Script(script.Script):
         self._sayAllContexts = []
 
         if app:
-            app.setCacheMask(pyatspi.cache.DEFAULT ^ pyatspi.cache.NAME)
+            app.setCacheMask(
+                pyatspi.cache.DEFAULT ^ pyatspi.cache.CHILDREN ^ pyatspi.cache.NAME)
 
     def setupInputEventHandlers(self):
         """Defines InputEventHandler fields for this script that can be