diff options
| author | dmazzoni <dmazzoni@chromium.org> | 2015-08-06 18:02:15 -0700 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-08-07 01:03:09 +0000 |
| commit | 1efe8793da85ee6e25185175047c077adfe8e55c (patch) | |
| tree | 3da8b088c3c997fca1d8b4e652819f8db1e415d9 /content/browser/accessibility/browser_accessibility.h | |
| parent | f54108dd9aa8b43982c206442664cb325cd792d7 (diff) | |
| download | chromium_src-1efe8793da85ee6e25185175047c077adfe8e55c.zip chromium_src-1efe8793da85ee6e25185175047c077adfe8e55c.tar.gz chromium_src-1efe8793da85ee6e25185175047c077adfe8e55c.tar.bz2 | |
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}
Diffstat (limited to 'content/browser/accessibility/browser_accessibility.h')
| -rw-r--r-- | content/browser/accessibility/browser_accessibility.h | 5 |
1 files changed, 0 insertions, 5 deletions
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 |