Open Bug 75618 Opened 24 years ago Updated 2 years ago

CR line breaks not recognized when inserting data in a plain text editor

Categories

(Core :: DOM: Editor, defect, P5)

PowerPC
Windows NT
defect

Tracking

()

mozilla1.4beta

People

(Reporter: bugzilla, Unassigned)

References

Details

(Whiteboard: [cr/lf])

Since we stop converting line ending to LF in msgCompose.cpp (see bug 74901), we are not able to reply to a message on Mac in plain text mode. I have checked in a temporary fix for that (see bug 75498) but we need to fix this problem inside editor. Looks like that the code that convert line ending to <BR> looks only for LF!
Blocks: 22486
Long ago, I wrote code for the editor to accept any kind of newline. Joe flagged it and pointed out that it would create a big performance hit everywhere that text was ever inserted, because of the newline translation we have to do. I think he timed it both ways. The editor team discussed it and eventually we decided to accept only DOM newlines for performance reasons. Add this to the long list of "problems that would go away if layout would let us have frames on blank lines".
-> joe
Assignee: beppe → jfrancis
moz 0.9 - fix in hand
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9
fix checked in
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
ducarroz, is this working for you now ?
Let me do some testing...
Nope, it still doesn't work. If I undo the fix for bug 75498 which was the workaround, then the original problem, bug 74901, is back! Sorry, reopen...
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
SPAM: mozilla 0.9 (and M1, and 0.8.1, etc.) has left the building. please update the target milestone so we can get a good idea of what's left for 0.9.1.
moving to 9.2
Priority: -- → P3
Target Milestone: mozilla0.9 → mozilla0.9.2
Keywords: correctness
Whiteboard: [cr/lf]
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Target Milestone: mozilla0.9.3 → mozilla1.0
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 (you can query for this string to delete spam or retrieve the list of bugs I've moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
Keywords: mozilla1.0+
The days of having a half dozen milestones out in front of us to divide bugs between seem to be gone, though I dont know why. Lumping everything together as far out as I can. I'll pull back things that I am working on as I go.
Target Milestone: mozilla1.0.1 → mozilla1.2beta
[ushing these out as far as bugzilla will let me. I'll pull them back as I work on them.
Target Milestone: mozilla1.2beta → mozilla1.4beta
Mach-O uses LF instead of CR, right?
QA Contact: sujay → editor
Assignee: mozeditor → nobody
Status: REOPENED → NEW

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: P3 → P5
You need to log in before you can comment on or make changes to this bug.