Only fire accessible load complete events on the main frame on Android.

content/browser/accessibility/browser_accessibility_manager_android.cc

Index: content/browser/accessibility/browser_accessibility_manager_android.cc
diff --git a/content/browser/accessibility/browser_accessibility_manager_android.cc b/content/browser/accessibility/browser_accessibility_manager_android.cc
index 20599dc90586bd1141725740018226574f70a1d7..e6e26f89cc5104d490496a204d41f6e952899775 100644
--- a/content/browser/accessibility/browser_accessibility_manager_android.cc
+++ b/content/browser/accessibility/browser_accessibility_manager_android.cc
@@ -217,6 +217,12 @@ void BrowserAccessibilityManagerAndroid::NotifyAccessibilityEvent(
     return;
   }
 
+  // Ignore load complete events on iframes.
+  if (event_type == ui::AX_EVENT_LOAD_COMPLETE &&
+      node->manager() != GetRootManager()) {
+    return;
+  }
+
   // Always send AccessibilityEvent.TYPE_WINDOW_CONTENT_CHANGED to notify
   // the Android system that the accessibility hierarchy rooted at this
   // node has changed.

[David Tseng, 2016/04/18 23:21:56]

Do you still need to do this?

[dmazzoni, 2016/04/19 18:52:23]

Yes, Peter says it's definitely needed for BrailleBack, because it could
possibly affect the content of the current braille line.

[David Tseng, 2016/04/19 20:36:30]

I wasn't clear, sorry: in the case of a load complete on a frame, do you need to
do this?