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

Issue 691282 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug
Team-Accessibility



Sign in to add a comment

Focus events should not always be fired before all other events

Project Member Reported by nek...@chromium.org, Feb 11 2017

Issue description

This is a bug affecting Jaws.
1. Start Google Docs and load a document.
2. Open a dialog, such as Tools > Preferences or File > Sharing.
3. Press escape.
4. Notice that focus doesn't land back in the document and actually gets completely lost requiring Alt+Tabbing to get back.

Cause:
We always fire focus events before all other events. This doesn't always work, because some focus events might be discarded if they don't arrive in the correct order related to other events.
 
Labels: NewComponent-Accessibility NewComponent-Accessibility-Compatibility
Components: UI>Accessibility>Compatibility
Components: -UI>Accessibility
Labels: -newcomponent-accessibility-compatibility -newcomponent-accessibility
Labels: triage-lpalmaro
Cc: -chaok@chromium.org
Labels: -triage-lpalmaro
Nektarios, is the status of started still correct here or should this be moved to available? 

Comment 6 by nek...@chromium.org, Dec 10 2017

Labels: a11y-secondary
Status: Available (was: Started)
Labels: Docs-specific
Status: Assigned (was: Available)

Sign in to add a comment