Closed Bug 183763 Opened 22 years ago Closed 19 years ago

hitting return after quoted text inserts newlines UNDER the cursor

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: temp6, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130

Hitting return to insert newlines between quoted text and text about to be typed
causes the newlines to be inserted after the cursor, which means I need to
scroll down with the cursor keys to get to the where I want to type.

Reproducible: Always

Steps to Reproduce:
1.Reply to message
2.Click within quoted text
3.Hit return a few times

Actual Results:  
Newlines inserted after the cursor

Expected Results:  
Cursor moves down as I hit return/newlines inserted at (before) cursor.
QA Contact: olgam → esther
I see this with 1.3b under linux as well.
| this is a test line.

If I move the cursor to before "test" and hit return to insert
a new line, I would expect the text to become

| this is a 
test line

But mozilla tries to be smart and add "|" before the second line.
But I get an extra newline as reported here and so the result is

| this is a

| test line

and the cursor is on the line between the two quoted ("|") lines.

This is rather annoying and in the serious problem category.


Product: Browser → Seamonkey
Assignee: sspitzer → mail
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.