| Issue 23669: | Chrome Frame does not enable current renderer accessibility flags | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
Chrome Frame currently does not pass the --enable-renderer-accessibility flag. A11y events should be passed as they are generated from renderers. |
||||||||||||||||||
,
Oct 06, 2009
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=28081
------------------------------------------------------------------------
r28081 | slightlyoff@chromium.org | 2009-10-05 18:04:48 -0700 (Mon, 05 Oct 2009) | 6 lines
Changed paths:
M http://src.chromium.org/viewvc/chrome/trunk/src/chrome_frame/chrome_frame_automation.cc?r1=28081&r2=28080
M http://src.chromium.org/viewvc/chrome/trunk/src/chrome_frame/chrome_launcher.cc?r1=28081&r2=28080
Pass the renderer a11y flag to Chrome Frame-created renderers.
BUG=23669
TEST=watch event32 a11y event log on pages which render in GCF.
Review URL: http://codereview.chromium.org/255062
------------------------------------------------------------------------
|
|||||||||||||||||||
,
Oct 06, 2009
(No comment was entered for this change.)
Status: Fixed
Cc: kl...@chromium.org |
|||||||||||||||||||
| ► Sign in to add a comment | |||||||||||||||||||