Closed Bug 262787 Opened 21 years ago Closed 21 years ago

Plugin finder bar is not accessible from keyboard

Categories

(Firefox :: Disability Access, defect)

1.0 Branch
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 220626

People

(Reporter: Maniac, Assigned: aaronlev)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040922 Firefox/0.10 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040922 Firefox/0.10 I mean the bar that pops up on the top of the page saying that "Additional plugins are required...". The button on the right - "Install Missing Plugins..." doesn't have an obvious keyboard shortcut. However, one may TAB there focusing first the location bar. But after button is focused pressing ENTER doesn't do anything and pressing SPACE does visually presses the button but PFS won't start anyway. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20041005 Firefox/0.10 Confirming 1) Only using tab will bring you to the [install Missing Plugin] button 2) Even if [install Missing Plugin] has focus , pressing [enter] won't do anything 3) you cannot focus on [X] to close the plugin installer bar -> New -> ?1.0
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking-aviary1.0?
see also bug 220626 for the popup notification bar (which has been minused).
OS: Windows XP → All
Hardware: PC → All
Version: unspecified → 1.0 Branch
See Bug 220626 comment #10 . It implies that no keyboard shortcut will be given.
Then may be it would be better to dupe this bug against bug 220626. And also rename its summary to something like 'Enable keyboard access to Info bar ("Blocked Popups", "Plugin Finder")' for better discoverability. Does anyone mind?
done. *** This bug has been marked as a duplicate of 220626 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
Flags: blocking-aviary1.0?
You need to log in before you can comment on or make changes to this bug.