Fixes an issue where the MSAA information was not reported back correctly to the AT, upon the HWND containing the web content first receiving focus. Note that this is not a full fix for the bug below, but one more piece to resolving it.BUG=13291TEST=none

Review URL: http://codereview.chromium.org/118206

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

1 files changed, 0 insertions, 13 deletions

diff --git a/chrome/browser/browser_accessibility.h b/chrome/browser/browser_accessibility.h
index c8d4187..43b8b19 100644
--- a/chrome/browser/browser_accessibility.h
+++ b/chrome/browser/browser_accessibility.h
@@ -116,11 +116,6 @@ class ATL_NO_VTABLE BrowserAccessibility
   }
   int instance_active() const { return instance_active_; }
 
-  void set_direct_descendant(bool direct_descendant) {
-    direct_descendant_ = direct_descendant;
-  }
-  bool direct_descendant() const { return direct_descendant_; }
-
   int routing_id() const { return routing_id_; }
 
  private:
@@ -171,14 +166,6 @@ class ATL_NO_VTABLE BrowserAccessibility
 
   HWND parent_hwnd_;
 
-  // Indicates if an incoming request for child information relates to a child
-  // id of a direct child of the BrowserAccessibility object, or if it refers
-  // to an object elsewhere in the MSAA tree. Set by BrowserAccessibilityManager
-  // and applicable only to the root BrowserAccessibility object (id 0). Needed
-  // to properly handled MSAA focus events, where the child id is the only
-  // parameter in our control.
-  bool direct_descendant_;
-
   // The instance should only be active if there is a non-terminated
   // RenderProcessHost associated with it. The BrowserAccessibilityManager keeps
   // track of this state, and sets it to false to disable all calls into the