Closed Bug 5303 Opened 26 years ago Closed 25 years ago

Control-# keys not working

Categories

(Core :: DOM: UI Events & Focus Handling, defect, P3)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: buster, Assigned: joki)

References

Details

In my tree from several days ago (code from around 4/15), I hooked up some editor methods to key strokes like Control-1, Control-2, etc. because I don't have any UI for testing these methods yet. In a tree pulled today (4/19), the editor key listeners no longer get KeyDown notifications for Control-[number]. But they do for Control-[letter]. This is true in viewer editor mode, and apprunner -editor
OS: Windows NT → All
Hardware: PC → All
Target Milestone: M14
this bug has to do with the control key, the corresponding keyevent, and its charCode and keyCode values. We currently have a hack (of sorts) in nsEventStateManager.cpp where we add "64" to the charCode if the control key is modified. set to M14 (post-beta); change to ALL platforms/os since this isn't windows- specific
Blocks: 15693
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
resolving this as fixed to get on QA radar. Jan--you'll be able to verify this once we have shortcuts in the task menu (*-1 for Navigator, *-2 for Messenger, etc.)
Keywords: verifyme
Mass update: changing qacontact to ckritzer@netscape.com
QA Contact: janc → ckritzer
Updating QA Contact.
QA Contact: ckritzer → lorca
akkana, does this sound familiar?
Timeless: note the dates. This is an ancient bug, referring to code more than a year old. There have been quite a few bugfixes, improvements, and also changes to the spec (we're not adding 64 or anything like that) since then.
Marking VERIFIED, but I can't regress this properly. Wee bit too old, no new comments, marked FIXED over a year ago...Any objections?
Status: RESOLVED → VERIFIED
URL: any
Keywords: verifyme
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.