Open Bug 249093 Opened 20 years ago Updated 2 years ago

Forward Inline does not reflow f=f text

Categories

(MailNews Core :: Composition, defect)

defect

Tracking

(Not tracked)

People

(Reporter: mcow, Unassigned)

References

Details

When an f=f text message or an HTML message with long source lines is replied to, the quoted text block is reflowed to the wrap column preference (except see bug 173918). When a non-f=f text message with long source lines is replied to, the quoted text block length is maintained. However, when forwarding inline as plain text, the long source lines of any plain message is simply wrapped to the wrap column, without reflowing, generating the "comb effect" on the forwarded text. When forwarding as HTML, the body of a plain text message, or of an HTML message viewed As Plain, is placed within a <pre> block and the original line lengths are maintained. HTML and f=f messages are not reflowed. Rewrap does not help either situation (see bug 237558). Actual results: text is not reflowed and, in plain text, is wrapped to bogus effect. Expected results: f=f plain and HTML viewed As Text should always be reflowed, and (for HTML composition) not placed within a <pre> block. Non-f=f plain should maintain the full length of the lines and be displayed during composition as long, unwrapping lines (as is done with the quote for Reply). See also bug 208128.
(In reply to comment #0) > when forwarding inline as plain text, the long source lines of any > plain message is simply wrapped to the wrap column, without reflowing, > generating the "comb effect" on the forwarded text. I realize now that my expectations for forwarding (as plain) a text/plain, non-f=f message are different from this; I have opened bug 262476 about this case. This bug is only about forwarding f=f mail. > When forwarding as HTML, the body of a plain text message, or of an HTML > message viewed As Plain, is placed within a <pre> block and the original > line lengths are maintained. HTML and f=f messages are not reflowed. That last bit is incorrect; I didn't examine my test case fully. Long source lines within HTML messages are handled correctly for inline forwarding, as HTML or as plain. > Expected results: f=f plain and HTML viewed As Text should always be reflowed, > and (for HTML composition) not placed within a <pre> block. Except for an HTML message with long lines *contained with a <pre> tag* in the original -- again, bug 262476. To summarize: 1) When forwarding inline as text/plain, a f=f message should be *reflowed*, not simply rewrapped as is the case now. 2) When forwarding as HTML, a f=f message should be reflowed, not wrapped in a <pre> block as is the case now. <br> tags should be added to the ends of lines which start a new paragraph under f=f.
OS: Windows 2000 → All
Hardware: PC → All
Summary: Forward Inline does not properly wrap/reflow forwarded plain text → Forward Inline does not reflow f=f text
Product: MailNews → Core
*** Bug 265406 has been marked as a duplicate of this bug. ***
*** Bug 285187 has been marked as a duplicate of this bug. ***
*** Bug 317740 has been marked as a duplicate of this bug. ***
*** Bug 348226 has been marked as a duplicate of this bug. ***
sorry for the spam. making bugzilla reflect reality as I'm not working on these bugs. filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
QA Contact: composition
Product: Core → MailNews Core
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.