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)
Tracking
()
NEW
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!
Comment 1•24 years ago
|
||
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".
Comment 3•24 years ago
|
||
moz 0.9 - fix in hand
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9
Comment 4•24 years ago
|
||
fix checked in
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 6•24 years ago
|
||
Let me do some testing...
Reporter | ||
Comment 7•24 years ago
|
||
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 → ---
Comment 8•24 years ago
|
||
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.
Updated•24 years ago
|
Keywords: correctness
Whiteboard: [cr/lf]
Updated•23 years ago
|
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Updated•23 years ago
|
Target Milestone: mozilla0.9.3 → mozilla1.0
Comment 10•23 years ago
|
||
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
Updated•23 years ago
|
Keywords: mozilla1.0+
Comment 11•22 years ago
|
||
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
Comment 12•22 years ago
|
||
[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
Comment 13•22 years ago
|
||
Mach-O uses LF instead of CR, right?
Updated•18 years ago
|
QA Contact: sujay → editor
Updated•18 years ago
|
Assignee: mozeditor → nobody
Status: REOPENED → NEW
Comment 14•4 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: P3 → P5
Comment 15•2 years ago
|
||
In bug 1478564, I stopped TextEditor
receiving text containing \r
.
https://searchfox.org/mozilla-central/rev/7426a35738cd542b9488c7b67f4f6d21edfeda0a/editor/libeditor/TextEditSubActionHandler.cpp#296
However, I don't see sanitation in HTMLEditor
.
https://searchfox.org/mozilla-central/rev/7426a35738cd542b9488c7b67f4f6d21edfeda0a/editor/libeditor/HTMLEditorDataTransfer.cpp#1931
So I guess this is still valid... (Although there is no platform using solo \r
as a linebreak.)
You need to log in
before you can comment on or make changes to this bug.
Description
•