421121 - keydown events are missing for control keys on Mac

Status: RESOLVED WORKSFORME

(Firefox :: Shell Integration, defect)

Description

[Paul Kleppner]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3) Gecko/2008020514 Firefox/3.0b3
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b3) Gecko/2008020511 Firefox/3.0b3

In Firefox 3 beta 3 on the Mac, when listening for keyup/down/press events on a design-mode edit control, the control keys are not firing the correct event sequence. For example, when pressing and releasing CTRL-G, the Mac gets this sequence of events:

keyDown for CTRL key
keyUp for "G"
keyUp for CTRL

Notice that there is no keyDown for the G.  With FF3 beta 3 on Windows, we get this sequence:

keyDown for CTRL
keyDown for "G"
keyPress 
keyUp for "G"
keyUp for CTRL

FF2 on the Mac also produces a similar correct sequence.

I'll attach a page with script which can demonstrate the problem.

One consequence of this: when using gmail or Google Docs, CTRL-B does not work to bold a word in FF Beta 3 on the Mac. I expect the same consequence for all web apps that want to process control keys.


Reproducible: Always

Steps to Reproduce:
1. Run attached "key.html"
2. Click in top pane to get focus, and press CTRL-G
3. Look at event log sequence that is reported in lower pane.
Actual Results:  
On Mac, with FF3 Beta 3, there is no key-down event for the "G".

Expected Results:  
Expect to see a key-down event for the "G"

Comment 1

[Paul Kleppner]

Attachment: Demonstrates events generated on keystrokes

With FF3 beta 3 on Mac, this page demonstrates missing key-down events for control keys.  With FF3 beta 3 on Windows, or FF2 on the mac, the correct key-down events are generated.

Comment 2

[Steven Michaud [:smichaud] (Retired)]

Is this still a problem in the current nightlies?

Comment 3

[Paul Kleppner]

I did try the beta 4 release candidate build after filing this bug, and the bug does seem to be fixed there. (There's another issue I see with CMD-X, CMD-C, CMD-V not being handled, but I'm still investigating and will file a separate bug on that.)