Focus event fired for accessible in previously active tab after opening a new tab from menu

VERIFIED FIXED in mozilla10

Status

()

Core
Disability Access APIs
VERIFIED FIXED
7 years ago
6 years ago

People

(Reporter: Jamie, Assigned: surkov)

Tracking

(Blocks: 2 bugs, {access, regression})

Trunk
mozilla10
x86
Windows 7
access, regression
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
Str:
1. Open a document in one tab.
2. Press alt+f to access the File menu, then select New Tab.
Expected: A focus event should be fired on the Location bar.
Actual: A focus event is (correctly) fired on the Location Bar. However, a focus event is then incorrectly fired in the previously active tab (step 1), thus overriding the correct focus.

This occurs whenever a new tab is opened using a menu; e.g. History -> Recently Closed Tabs or Tools -> Add-ons Manager. It does not occur when opening new tabs using keyboard shortcuts (and I assume clicking buttons); e.g. control+t.

This bug means that focus appears to be in the previous document when screen reader users open a new tab from a menu. Screen reader users have to move the focus in some way to restore focus to the correct tab, which is annoying at best and extremely confusing at worst.

This does not occur in Firefox 3.6.
(Assignee)

Updated

7 years ago
Blocks: 375743
(Reporter)

Updated

6 years ago
Blocks: 659863
(Assignee)

Comment 1

6 years ago
Jamie, I can't see it on trunk. Can you?
(Reporter)

Comment 2

6 years ago
I can still reproduce this 100% using trunk (Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0a1) Gecko/20110917 Firefox/9.0a1).
(Assignee)

Comment 3

6 years ago
still can't reproduce, anyway, let's try it again after bug 673958 is fixed
(Reporter)

Comment 4

6 years ago
I verified that this is fixed in the last try build for bug 673958.
Depends on: 673958
(Assignee)

Comment 5

6 years ago
fixed by bug 673958
Assignee: nobody → surkov.alexander
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla10

Comment 6

6 years ago
Verified fixed in Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0a1) Gecko/20110929 Firefox/10.0a1
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.