New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 23669 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit 18 days ago
Closed: Oct 2009
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug

Restricted
  • Only users with Commit permission may comment.



Sign in to add a comment

Chrome Frame does not enable current renderer accessibility flags

Project Member Reported by slightlyoff@chromium.org, Oct 2 2009

Issue description

Chrome Frame currently does not pass the --enable-renderer-accessibility 
flag. A11y events should be passed as they are generated from renderers.
 
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
------------------------------------------------------------------------

Status: Fixed
Labels: -Area-ChromeFrame bulkmove Feature-ChromeFrame
Project Member

Comment 4 by bugdroid1@chromium.org, Oct 13 2012

Labels: Restrict-AddIssueComment-Commit
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
Project Member

Comment 5 by bugdroid1@chromium.org, Mar 11 2013

Labels: -Feature-ChromeFrame Cr-ChromeFrame

Sign in to add a comment