Send Android accessibility "content changed" event for any change.

Specifically, AccessibilityEvent.TYPE_WINDOW_CONTENT_CHANGED should
be fired on the appropriate node any time the accessibility tree changes
- previously we were only firing it in a few circumstances. That guarantees
tools like uiautomatorviewer won't see a stale accessibility tree.

BUG=286374

Review URL: https://chromiumcodereview.appspot.com/23481011

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@221853 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 6 insertions, 3 deletions

diff --git a/content/browser/accessibility/browser_accessibility_manager_android.cc b/content/browser/accessibility/browser_accessibility_manager_android.cc
index a4c1965..2943c5c 100644
--- a/content/browser/accessibility/browser_accessibility_manager_android.cc
+++ b/content/browser/accessibility/browser_accessibility_manager_android.cc
@@ -90,6 +90,12 @@ void BrowserAccessibilityManagerAndroid::NotifyAccessibilityEvent(
   if (obj.is_null())
     return;
 
+  // Always send AccessibilityEvent.TYPE_WINDOW_CONTENT_CHANGED to notify
+  // the Android system that the accessibility hierarchy rooted at this
+  // node has changed.
+  Java_BrowserAccessibilityManager_handleContentChanged(
+      env, obj.obj(), node->renderer_id());
+
   switch (event_type) {
     case WebKit::WebAXEventLoadComplete:
       Java_BrowserAccessibilityManager_handlePageLoaded(
@@ -131,9 +137,6 @@ void BrowserAccessibilityManagerAndroid::NotifyAccessibilityEvent(
       if (node->IsEditableText()) {
         Java_BrowserAccessibilityManager_handleEditableTextChanged(
             env, obj.obj(), node->renderer_id());
-      } else {
-        Java_BrowserAccessibilityManager_handleContentChanged(
-            env, obj.obj(), node->renderer_id());
       }
       break;
     default: