can't type "n" in a text input field in the message display

VERIFIED FIXED in M14

Status

P3
normal
VERIFIED FIXED
19 years ago
14 years ago

People

(Reporter: sspitzer, Assigned: hangas)

Tracking

Trunk
x86
Linux

Firefox Tracking Flags

(Not tracked)

Details

try this:

send yourself this page: 

http://bugzilla.mozilla.org/enter_bug.cgi?product=MailNews

go to messenger, read that message, and try to type

"that was then, this is now" in the text areas.

you'll get

"that was the, this is ow"

it looks like all the other characters (lower case, at least)
are being let through.

Comment 1

19 years ago
Sounds like an editor thing. Reassign to brade.
Assignee: phil → brade
(Assignee)

Comment 2

19 years ago
This looks like the key binding for Next Unread Message that I added last week.  
I can pull that code out, it was in there so that we could track down the bug 
that was keeping it from working.  It looks like it only affected the text input 
fields but did not make it to the menu it was connected to.  Taking bug.
Status: NEW → ASSIGNED
Target Milestone: M14

Comment 3

19 years ago
reassign to hangas per his comment
Assignee: brade → hangas
Status: ASSIGNED → NEW
(Assignee)

Updated

19 years ago
Status: NEW → ASSIGNED
Keywords: beta1
(Assignee)

Comment 4

19 years ago
Fix checked in.  Removed key binding for Next Unread Message because it causes 
this problem.  We need to redo the way key events are handled to add this key 
binding back in for the Next Unread Message menu item, but that is another bug...
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED

Updated

19 years ago
QA Contact: lchiang → fenella

Comment 5

19 years ago
Linux (2000-02-23-08 M14)
Win32 (2000-02-23-09 M14)
Linux (2000-02-23-12 M14)
Following the scenario as described. The bug is gone. 
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.