diff options
author | dtseng@chromium.org <dtseng@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-05-14 01:02:47 +0000 |
---|---|---|
committer | dtseng@chromium.org <dtseng@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-05-14 01:02:47 +0000 |
commit | 457af8d4fd866e1b40649a15943f9f7329cfcc38 (patch) | |
tree | 66e87dd380a09090cc9d66593af54cd0e955aedb /chrome/common/switch_utils_unittest.cc | |
parent | 0e10cb5cb75c2ef241f46c0430b8fdc570518810 (diff) | |
download | chromium_src-457af8d4fd866e1b40649a15943f9f7329cfcc38.zip chromium_src-457af8d4fd866e1b40649a15943f9f7329cfcc38.tar.gz chromium_src-457af8d4fd866e1b40649a15943f9f7329cfcc38.tar.bz2 |
Support the AXRows and AXColumns attributes. We do this by examining the AX hieararchy exposed by webkit (specifically our own cache of it in BrowserAccessibility's). Table ax elements always have its associated rows and columns as immediate children.
I also looked into passing this information over from WebKit with a sample patch. It would involve exposing AccessibilityTable accessors within WebAccessibilityObject, adding additional members to WebAccessibility to be shipped over (renderer id's or elements themselves.
Presenting this alternative since it was easy to implement and can be generalized for Windows as well by pushing this up to BrowserAccessibility.
BUG=66719
TEST=manually with VoiceOver.
Review URL: http://codereview.chromium.org/5862004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@85358 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/common/switch_utils_unittest.cc')
0 files changed, 0 insertions, 0 deletions