accesskeys on form elements do not work correctly on mac os x

RESOLVED WORKSFORME

Status

()

RESOLVED WORKSFORME
13 years ago
13 years ago

People

(Reporter: Mail, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.9) Gecko/20050711 Firefox/1.0.5
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.9) Gecko/20050711 Firefox/1.0.5

On http://www.jonas-hartmann.com/mozilla/#accesskeystuff accesskey b (invoked by
pressing ctrl+b) on an <input type="file" ... /> and accesskey f (invoked by
pressing ctrl+f, apple+f is find command) on an <select> do not work.

notice: on firefox on windows accesskey f works - even though xhtml 1.0 strict
specifies that <select> cannot have accesskey="" attribute.

Reproducible: Always

Steps to Reproduce:
1. Load http://www.jonas-hartmann.com/mozilla/#accesskeystuff
2. hit CTRL+A, CTRL+B... ...CTRL+F

Actual Results:  
1. Some accesskeys work, some dont (those on input type="file" and select it seems)

Expected Results:  
selecting the form elements when the accesskey is invoked/pressed
(Reporter)

Updated

13 years ago
Component: Disability Access → Keyboard Navigation
(Reporter)

Comment 1

13 years ago
Created attachment 189623 [details]
tabindex/accesskey teest case

Comment 2

13 years ago
All work for me in Deer Park Alpha 2, on Mac OS X 10.2
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050717
Firefox/1.0+
(Reporter)

Comment 3

13 years ago
correct.
works on 10.3.9 Firefox Deer Park Alpha 2
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → FIXED
Reopen to resolve WFM as no relevant code change identified which caused the fix.
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Resolve WFM as per comment 3
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.