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

content/browser/accessibility/browser_accessibility_manager_android.cc

 // Copyright 2013 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 "content/browser/accessibility/browser_accessibility_manager_android.h"
 
 #include <stddef.h>
 
 #include <cmath>
 
@@ skipping 199 matching lines @@
 
   // Layout changes are handled in OnLocationChanges.
   if (event_type == ui::AX_EVENT_LAYOUT_COMPLETE)
     return;
 
   if (event_type == ui::AX_EVENT_HOVER) {
     HandleHoverEvent(node);
     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?

   Java_BrowserAccessibilityManager_handleContentChanged(
       env, obj.obj(), node->unique_id());
 
   switch (event_type) {
     case ui::AX_EVENT_LOAD_COMPLETE:
       Java_BrowserAccessibilityManager_handlePageLoaded(
           env, obj.obj(), GetFocus()->unique_id());
       break;
     case ui::AX_EVENT_FOCUS:
       Java_BrowserAccessibilityManager_handleFocusChanged(
@@ skipping 706 matching lines @@
 
   JNIEnv* env = AttachCurrentThread();
   return root_manager->java_ref().get(env);
 }
 
 bool RegisterBrowserAccessibilityManager(JNIEnv* env) {
   return RegisterNativesImpl(env);
 }
 
 }  // namespace content