Implement support for accessible collapse and expand actions on Android

content/browser/accessibility/browser_accessibility_android.cc

Index: content/browser/accessibility/browser_accessibility_android.cc
diff --git a/content/browser/accessibility/browser_accessibility_android.cc b/content/browser/accessibility/browser_accessibility_android.cc
index abe3a0164383e834b154b5fef928a17cb81e6355..991cf010d1fdacd439e518233aeabe27b3dd6c25 100644
--- a/content/browser/accessibility/browser_accessibility_android.cc
+++ b/content/browser/accessibility/browser_accessibility_android.cc
@@ -162,6 +162,10 @@ bool BrowserAccessibilityAndroid::IsClickable() const {
   return IsFocusable() || !GetText().empty();
 }
 
+bool BrowserAccessibilityAndroid::IsCollapsed() const {
+  return HasState(ui::AX_STATE_COLLAPSED);
+}
+
 bool BrowserAccessibilityAndroid::IsCollection() const {
   return (GetRole() == ui::AX_ROLE_GRID ||
           GetRole() == ui::AX_ROLE_LIST ||
@@ -198,6 +202,10 @@ bool BrowserAccessibilityAndroid::IsEnabled() const {
   return !HasState(ui::AX_STATE_DISABLED);
 }
 
+bool BrowserAccessibilityAndroid::IsExpanded() const {
+  return HasState(ui::AX_STATE_EXPANDED);

[David Tseng, 2016/08/24 22:46:13]

Is a widget ever both expanded and collapsed at the same time?

[dmazzoni, 2016/08/24 22:56:05]

No, we enforce that in content/renderer/accessibility - Blink
returns an enum (none, collapsed, expanded) and we turn it into
a state from there.

We could probably switch to using the enum everywhere internally,
it only looks this way because most platform APIs have separate
flags for collapsed and expanded rather than a single enum

+}
+
 bool BrowserAccessibilityAndroid::IsFocusable() const {
   bool focusable = HasState(ui::AX_STATE_FOCUSABLE);
   if (IsIframe() ||