From 1efe8793da85ee6e25185175047c077adfe8e55c Mon Sep 17 00:00:00 2001 From: dmazzoni Date: Thu, 6 Aug 2015 18:02:15 -0700 Subject: Get rid of FrameAccessibility using AXTreeIDs Depends on: https://codereview.chromium.org/1257093005/ Instead of keeping track of the relationship between frames in FrameAccessibility, create a subclass of AXNodeData that's only allowed to be used within the content module, and once an AX tree is received in the browser process, convert routing IDs to global AXTreeIDs that can be stored AXNodeData. BUG=368298 Review URL: https://codereview.chromium.org/1267663002 Cr-Commit-Position: refs/heads/master@{#342251} --- content/browser/accessibility/browser_accessibility.h | 5 ----- 1 file changed, 5 deletions(-) (limited to 'content/browser/accessibility/browser_accessibility.h') diff --git a/content/browser/accessibility/browser_accessibility.h b/content/browser/accessibility/browser_accessibility.h index 17297ba..679becf 100644 --- a/content/browser/accessibility/browser_accessibility.h +++ b/content/browser/accessibility/browser_accessibility.h @@ -282,11 +282,6 @@ class CONTENT_EXPORT BrowserAccessibility { // including this object if it's static text. int GetStaticTextLenRecursive() const; - // Similar to GetParent(), but includes nodes that are the host of a - // subtree rather than skipping over them - because they contain important - // bounds offsets. - BrowserAccessibility* GetParentForBoundsCalculation() const; - // If a bounding rectangle is empty, compute it based on the union of its // children, since most accessibility APIs don't like elements with no // bounds, but "virtual" elements in the accessibility tree that don't -- cgit v1.1