Open Bug 179318 Opened 18 years ago Updated 14 years ago
Plain Text Editor has apparent blank lines when inserting text
User-Agent: Mozilla/5.0 (X11; U; OpenVMS COMPAQ_AlphaServer_DS10_466_MHz; en-US; rv:1.2b) Gecko/20021022 Build Identifier: Mozilla/5.0 (X11; U; OpenVMS COMPAQ_AlphaServer_DS10_466_MHz; en-US; rv:1.2b) Gecko/20021022 When inserting text in the middle of a quoted section, it appears that blank lines are inserted before and after the inserted section, when they really are not. This means that the formatting during the compose of plain text message does not represent how the end user is going to see the results. Sometimes it is not possible to enter text at the bottom of a quoted section. The text appears to be appended to the end of the quoted section. The quoted sections are not properly wrapped. This was first observed with: Mozilla 1.2b Mozilla/5.0 (X11; U; OpenVMS COMPAQ_AlphaServer_DS10_466_MHz; en-US; rv:1.2b) Gecko/20021022 I did not see this problem with Mozilla M1.1 Reproducible: Always Steps to Reproduce: 1.Reply to a plain text message with several lines of quotes content 2.Place the cursor in the middle of a line and hit the return key to start a new line. 3. Actual Results: It appears that an additional blank line has been inserted on both sides of the new blank line. Expected Results: It should have only shown and inserted one blank line for each carriage return entered. http://bugzilla.mozilla.org/show_bug.cgi?id=174369 ------- Additional Comments From firstname.lastname@example.org 2002-11-05 11:51 ------- John: This fix definitely didn't introduce that bug, though it may have exposed it. Please file a bug to email@example.com, preferably checking his current buglist first to see if it's a dup of something he's already working on. I do not know how to check his current bug list, but I could not find anything using the Bugzilla search. I did find many problems that I have been seeing with the plain text editor listed. Most of the problems are with the insertion of characters or lines.
over to editor
Assignee: ducarroz → kin
Component: Composition → Editor: Core
Product: MailNews → Browser
QA Contact: esther → sujay
It is working much better now. It is making the assumption that when you press the enter key to break a quoted line, that you want to insert a blank line instead of just changing the formatting. This is usuable, as what you are seeing, is now what you are getting. To be consistent with the expected behavior of plain-text editors, it should just insert a line break, and not an additional blank line. Mozilla 1.3a Mozilla/5.0 (X11; U; OpenVMS COMPAQ_AlphaServer_DS10_466_MHz; en-US; rv:1.3a) Gecko/20021210
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/
The unexpected behavior of inserting two line breaks instead of one is still present. Mozilla 1.7 Mozilla/5.0 (X11; U; OpenVMS AlphaServer_DS10_617_MHz; en-US; rv:1.7) Gecko/20040621
You need to log in before you can comment on or make changes to this bug.