| commit | 28060a875c0a7fb9bbfe06a0057b4321518599a7 | |
| author | dmazzoni <dmazzoni@chromium.org> | |
| Mon, 19 Jan 2015 08:26:40 +0000 (19 00:26 -0800) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Mon, 19 Jan 2015 08:27:39 +0000 (19 08:27 +0000) | ||
| tree | 35d7dc083dedb1800dc2450ec84b86e127582f91 | treesnapshot (tar.gz zip) |
| parent | 763048e2c450f42af48e780b4c4377d7d6f555a1 | commitdiff |
Make Windows accessibility event firing aware of guest / child frames.
Windows-specific fixes for accessibility of out-of-process iframes
and guest frames (e.g. <webview>):
1. When firing an event or doing a bounds calculation, we need to
call functions on the root BrowserAccessibilityManager's delegate
(not on the child frame's delegate).
2. When a MSAA client tries to look up an MSAA object by child ID,
we need to search child frames as well.
BUG=330307, 368298
Review URL: https://codereview.chromium.org/799633007
Cr-Commit-Position: refs/heads/master@{#312080}
Windows-specific fixes for accessibility of out-of-process iframes
and guest frames (e.g. <webview>):
1. When firing an event or doing a bounds calculation, we need to
call functions on the root BrowserAccessibilityManager's delegate
(not on the child frame's delegate).
2. When a MSAA client tries to look up an MSAA object by child ID,
we need to search child frames as well.
BUG=330307, 368298
Review URL: https://codereview.chromium.org/799633007
Cr-Commit-Position: refs/heads/master@{#312080}