diff options
| author | dmazzoni <dmazzoni@chromium.org> | 2016-02-24 16:11:08 -0800 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2016-02-25 00:12:16 +0000 |
| commit | 4e143f588ee88f7e345abd261476f7721e48a428 (patch) | |
| tree | 6f2ea7c17fb3e7a20fb7d9eaee7ff2e72a2a7d2a /content/common/gpu/gpu_memory_manager.h | |
| parent | a6f677309a7741a1b9d6f6c510ee8282bfbff8c8 (diff) | |
| download | chromium_src-4e143f588ee88f7e345abd261476f7721e48a428.zip chromium_src-4e143f588ee88f7e345abd261476f7721e48a428.tar.gz chromium_src-4e143f588ee88f7e345abd261476f7721e48a428.tar.bz2 | |
Enable accessibility support when IAccessible2 is accessed from views.
A reliable signal that a third-party client wants full accessibility
support is using the IAccessible2 interface. (IAccessible is used for
too many other purposes.) Previously we only enabled full accessibility
support if a client used the IAccessible2 API inside the web frame,
but this sometimes failed to detect some screen readers if focus was
in views when they encounter Chrome.
Fix it so that AXPlatformNodeWin detects the usage of IAccessible2 and
use an Observer pattern to allow BrowserAccessibilityManagerWin to
trigger on that and enable full accessibility support if needed.
BUG=492623
Review URL: https://codereview.chromium.org/1732733003
Cr-Commit-Position: refs/heads/master@{#377430}
Diffstat (limited to 'content/common/gpu/gpu_memory_manager.h')
0 files changed, 0 insertions, 0 deletions