Closed Bug 371985 Opened 17 years ago Closed 16 years ago

Extension Manager looses focus of currently installed extension, confusing screen reader users.

Categories

(Toolkit :: Add-ons Manager, defect)

1.8.0 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: norman.b.robinson, Unassigned)

References

()

Details

(Keywords: access)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.10) Gecko/20070216 Firefox/1.5.0.10
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.10) Gecko/20070216 Firefox/1.5.0.10

When adding an extention add-on the extention screen focuses on whatever extention is in the middle of the extention window, rather than the extention currently being installed. 

Reproducible: Always

Steps to Reproduce:
1. Have several extentions installed.
2. Start JAWS screen reader
3. Install new extention and notice focus is not on the extension currently being installed; 
Actual Results:  
Screen reader reads the "middle" extension (half way down the list of extensions) instead.

Expected Results:  
Screen reader should retain focus on currently installed item, reading the description for that item, and not an extension previously installed.

JAWS for Windows 6.20.65U. This bug is particularly painful when you realize the use case for this consists of a user installing and expecting a extension and basically getting notified, by being read a different description for different extension, giving the impression they are installing the wrong extension!
Norman, do you see this with Firefox v2?
Keywords: access
Summary: Extention Manager looses focus of currently installed extention, confusing screen reader users. → Extension Manager looses focus of currently installed extension, confusing screen reader users.
Version: unspecified → 1.5.0.x Branch
=> incomplete due to no response

but maybe someone else can see it
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.