The Mac accessibility impl should defer to BrowserAccessibilityManager...

content/browser/accessibility/browser_accessibility_cocoa.mm

 // Copyright (c) 2011 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 <execinfo.h>
 
 #import "content/browser/accessibility/browser_accessibility_cocoa.h"
 
 #include <map>
 
@@ skipping 409 matching lines @@
 
   return @"";
 }
 
 - (NSNumber*)enabled {
   return [NSNumber numberWithBool:
       !GetState(browserAccessibility_, WebAccessibility::STATE_UNAVAILABLE)];
 }
 
 - (NSNumber*)focused {
+  BrowserAccessibilityManager* manager = browserAccessibility_->manager();
   NSNumber* ret = [NSNumber numberWithBool:
-      GetState(browserAccessibility_, WebAccessibility::STATE_FOCUSED)];
+      manager->GetFocus(NULL) == browserAccessibility_];

[David Tseng, 2011/11/30 20:49:33]

question: do we ever care that the previously focused item still has it's
focused state set?

[dmazzoni, 2011/11/30 22:02:27]

This change means that we're basically ignoring what state WebKit has set for an
object. BrowserAccessibilityManager keeps track of which item has focus and at
any instant in time, only one object will have the focused bit set when the AT
queries it.

   return ret;
 }
 
 - (NSString*)help {
   return NSStringForStringAttribute(
       browserAccessibility_->string_attributes(),
       WebAccessibility::ATTR_HELP);
 }
 
 // Returns whether or not this node should be ignored in the
@@ skipping 593 matching lines @@
     return [super hash];
   return browserAccessibility_->renderer_id();
 }
 
 - (BOOL)accessibilityShouldUseUniqueId {
   return YES;
 }
 
 @end