Closed Bug 23285 Opened 25 years ago Closed 24 years ago

<Enter> while in the multi-line edit field, Notes for a Card dialog, will close the dialog, it shouldn't

Categories

(SeaMonkey :: MailNews: Address Book & Contacts, defect, P3)

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: esther, Assigned: mjudge)

Details

Using build 2000010609 on win98, 2000010611 on Mac and 2000010515 on linux, if
you press <Enter> in the multi-line edit field for Notes in a Card dilaog will
close the card, when you really wanted to go to the next line.   This is a
spin-off of bug 21963 which stated <Enter> should close a dialog, however this
exception was noted in the comments.   Logging this for Address Book, since I
haven't found another dialog yet that has a multi-line edit field.  Note: 4.7
Address Card works correctly on all platforms.

1. Launch Messenger
2. Open Address Book
3. Select and Address Book and click New Card (or edit a card)
4. In the Card dialog, click on the Other tab, the put focus in the Notes area
5. Start typing then hit the <Enter> key to move to the next line.

Result: The card close
Expected: the cursor to go to the next line for more text entry.
QA Contact: lchiang → esther
Adding buster and sfraser to cc list, hoping one of them will take this bug.
This bug is not in the xul/js.  It must be in something deeper (possibly event
handling for html:textarea)
Assignee: hangas → buster
I'll take a look.
Target Milestone: M14
setting this to m14
this will have to wait for M17 if I am going to be the one to look into it.  If 
it needs to be addressed sooner, someone else will have to do some research into 
it.
Target Milestone: M14 → M17
Ender-lite might fix this.  If not, the editor folks should take a look.
Assignee: buster → beppe
assigning to Mike
Assignee: beppe → mjudge
fixed post ender-lite.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Using build 2000-08-28 on win98, mac and linux this is fixed. verified.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.