I'm not sure if this is a valid bug. For a keypress event you should *first* be checking for a *charcode* (not a keycode). Keycodes are only guaranteed to be set for keydown and keyup events.
But this is how it works on IE4, IE5 and NS4 browsers
*** Bug 58709 has been marked as a duplicate of this bug. ***
This is a dupe. The dupe points a problem in a high vis page so making this a dupe of that even though this was first... *** This bug has been marked as a duplicate of 58709 ***
Status: UNCONFIRMED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.