This bug seems related to bug 256954, which has been closed as a dup of 220900. I don't think this bug is a dup of 220900, though. I think this bug is specifically OS X related. And if that's true, then there's a good chance that 256954 is not actually a dup and should be reopened or duped to 335693.
This is probably related to some of our mac menu bugs. iirc once a menu have been opened it's the menu's shortcuts that takes over.
Assignee: nobody → joshmoz
Component: General → Widget: Mac
Product: Firefox → Core
QA Contact: general → mac
Version: unspecified → Trunk
This is probably a dupe of bug 417108.
Flags: blocking1.9? → blocking1.9+
Priority: -- → P1
Whatever the state of things were when this bug was reported have long since changed. The "listener stops receiving" aspect is no longer true: the page's js listener never receives cmd+c, ever, period. Testing with the attached example shows that *no* cmd+letter keypresses are received by the listener -- regardless of whether something is bound to them or not. All key combos involving command + a non-printable key (F keys, arrows) DO generate events, unless they're mapped to some OS function. However, in these cases the keyCode value reported is "0", which obviously isn't right. (Values like "63234" are reported in Safari.) That last bit holds in general: all non-printable except backspace and enter seem to report keyCode=0, regardless of modifiers. (The modifiers themselves seem to be reported correctly.) Chords involving ctrl (including ones that are bound) are received. On this test page, Safari does seem to pass the proper events down to the listener on the page in all cases except when the OS catches it (Exposé keys, for instance) and Safari itself doesn't receive the keypress. How much of this functionality SHOULD there be?
Component: Widget: Mac → Widget: Cocoa
QA Contact: mac → cocoa
Sorry about my comment before, I didn't read the bug closely enough. I have known about this bug for a long time, it is a limitation that our native menu architecture has. When a native menu item handles a command it eats the event after invoking the action. I have experimented with solving this in the past and we may be able to do it, but the change is really quite invasive and I wouldn't be comfortable taking it this late in the 1.9 cycle. We should make this a priority for Moz 2 though. The patch called "menus only visually handle key events" on 398514 is part of my attempt at exploring a solution for this issue.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking1.9+ → blocking1.9-
Priority: P1 → --
Fixed by the final patch on bug 398514.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.