Open
Bug 147898
Opened 22 years ago
Updated 3 years ago
joining/splitting lines doesn't work correctly
Categories
(Core :: DOM: Editor, defect, P5)
Tracking
()
UNCONFIRMED
People
(Reporter: davidmaxwaterman, Unassigned)
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; IRIX IP32; en-US; rv:1.0.0+) Gecko/20020527 BuildID: 2002052723 When composing a reply to a message, I often find it necessary to join or split lines. To do this I might go to the end of a line and hit 'Delete' to "eat" the CR. I also might go to the beginning of the next line and hit 'Backspace', also to "eat" the CR. To split a line in two, I might go to the position in the line and hit 'Enter'. I often find these attempts produce unexpected results. For example, in the instance that caused me to file this bug, I have the following text : > See what you think of the location. Downtown Mountain View is also convenient for me so > If this is too far or you do not like Indian food please suggest something else. > I eat just about any type of food. How does 11:30 sound for lunch. Hmm. Actually, that 'cut and paste'd correctly. In the compose window, it looks like this : > See what you think of the location. Downtown Mountain View is also convenient for me so > If this is too far or you do not like Indian food please suggest something else. > I eat just about any type of food. How does 11:30 sound for lunch. In other words, the '> ' at the start of the second line is shown on a different line to the 'If' - in the cut and paste, it put it on the same line. Interesting. The problem I was seeing was if I put the cursor on the end of the line with the single '> ', and hit 'Delete', it erases the 'I' from 'If' on the next line - it doesn't move the 'If...' line up one as expected. Also, going to the beginning of the 'If' line and hitting 'Backspace', deletes the space right after the '>' on the previous line, and moves the 'If...' line up : >If this is too far or you do not like Indian food please suggest something else. If I added the space again, it moved the 'If...' down again to the next line. Ah, after I cut and pasted the above but, it's stopped doing that now. Very odd behaviour. Not at all sure how that can be debugged. The interaction with cut and paste makes me think it isn't so much an editting issue as an issue with how the text is displayed. Any ideas? Max. Reproducible: Sometimes Steps to Reproduce: 1.reply to an email 2.try to join and split long lines using 'Delete' and 'Backspace' ad the beginning and end of lines, and 'Enter' in the middle of lines 3. Actual Results: doesn't behave as expected; too difficult to describe. Expected Results: should join and split as expected.
Comment 1•22 years ago
|
||
reassign to editor
Assignee: ducarroz → kin
Component: Composition → Editor: Core
Keywords: mailtrack
Product: MailNews → Browser
QA Contact: esther → sujay
Comment 2•22 years ago
|
||
does this still exist in 1.1beta?
Reporter | ||
Comment 3•22 years ago
|
||
I do still see odd behaviour when trying to edit quoted test - usually just trying to split something like : " > some text someone wrote to me. some more text " into : " > some text someone wrote to me. so I can insert my own comments here > some more text " It sometimes seem impossible to type in that second '>' without it pushing the text following it onto the next line - ie : " so I can insert my own comments here > some more text " I am wondering if my second line in the example above is a bad example, because, it occurs to me that, the lines are usually much longer, and it could be that the code which tried to enforce a maximum line length and which would normally split the line automatically, is doing something wrong with it; that wouldn't happen with a line which is short. But, yes, this is still not working correctly, though my overall impression is that it is behaving more predictably. (I have moved platform too; from IRIX/Linux to Mac OS X, so that might have effected things)
Reporter | ||
Comment 4•22 years ago
|
||
This problem still exists with 2002111303, but is very difficult to reproduce. You really need to use the email client extensively and perhaps there is an element of 'the way one works' that is needed in order to reproduce it. I will keep trying to figure out how to repeatedly reproduce it. Max.
Comment 6•22 years ago
|
||
kin, the fact that this pasted properly makes me wonder if this is a dup of 175837?
Comment 7•21 years ago
|
||
Max: is this still a problem? Do you have more consistent steps-to-reproduce?
Comment 8•20 years ago
|
||
marking WORKSFORME
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 9•20 years ago
|
||
I could not reproduce my original test, but there are still problems with this. For example, I sent myself the message : " some text someone wrote to me. " Then replied to it. I inserted a CR after the '.', and added the "so I can insert my own comments here" to arrive at : " Max Waterman wrote: > some text someone wrote to me. so I can insert my own comments here > some more text " I then click after the 'e' of 'some' and hit CR. This results in : " Max Waterman wrote: > some text someone wrote to me. so I can insert my own comments here > some more text " which has an extra CR inserted.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Comment 10•19 years ago
|
||
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/
Comment 11•19 years ago
|
||
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: 20 years ago → 19 years ago
Resolution: --- → EXPIRED
Reporter | ||
Comment 12•19 years ago
|
||
Still a problem
Status: RESOLVED → UNCONFIRMED
Resolution: EXPIRED → ---
Comment 13•18 years ago
|
||
This sounds like a problem with format flawed. You don't use the plain text editor, do you? Could also be one of those: bug 161968, bug 222344. pi
Reporter | ||
Comment 14•18 years ago
|
||
(In reply to comment #13) > This sounds like a problem with format flawed. You don't use the plain text > editor, do you? Of course I do. Max.
Updated•17 years ago
|
QA Contact: sujay → editor
Updated•17 years ago
|
Assignee: mozeditor → nobody
Comment 15•3 years ago
|
||
Bulk-downgrade of unassigned, >=3 years untouched DOM/Storage bug's priority.
If you have reason to believe this is wrong, please write a comment and ni :jstutte.
Severity: normal → S4
Priority: -- → P5
You need to log in
before you can comment on or make changes to this bug.
Description
•