Support AXContents attribute on the RenderWidgetHostViewCocoa....

chrome/browser/renderer_host/render_widget_host_view_mac.mm

Index: chrome/browser/renderer_host/render_widget_host_view_mac.mm
===================================================================
--- chrome/browser/renderer_host/render_widget_host_view_mac.mm	(revision 65217)
+++ chrome/browser/renderer_host/render_widget_host_view_mac.mm	(working copy)
@@ -1787,7 +1787,8 @@
 - (id)accessibilityAttributeValue:(NSString *)attribute {
   BrowserAccessibilityManager* manager =
       renderWidgetHostView_->browser_accessibility_manager_.get();
-  if ([attribute isEqualToString:NSAccessibilityChildrenAttribute] &&
+  if (([attribute isEqualToString:NSAccessibilityChildrenAttribute] ||
+          [attribute isEqualToString:NSAccessibilityContentsAttribute]) &&

[Chris Guillory, 2010/11/16 22:37:11]

Seems like it should be more clear that children and contents aren't the same.
Can we add a comment specifying that the contents of a render widget host view
cocoa element is the document view provided by the browser accessibility
manager?

       manager) {
     return [NSArray arrayWithObjects:manager->
         GetRoot()->toBrowserAccessibilityCocoa(), nil];
@@ -1798,6 +1799,13 @@
   return ret;
 }
 
+- (NSArray*)accessibilityAttributeNames {
+  NSMutableArray* ret = [[[NSMutableArray alloc] init] autorelease];
+  [ret addObject:NSAccessibilityContentsAttribute];
+  [ret addObjectsFromArray:[super accessibilityAttributeNames]];

[Chris Guillory, 2010/11/16 22:37:11]

Nit: Should we check/dcheck that NSAccessibilityContentsAttribute isn't added a
second time here?

+  return ret;
+}
+
 - (id)accessibilityHitTest:(NSPoint)point {
   if (!renderWidgetHostView_->browser_accessibility_manager_.get())
     return self;