Closed
Bug 104348
Opened 23 years ago
Closed 22 years ago
Editing draft (or other plain text message as new) loses flowed quoting information
Categories
(MailNews Core :: MIME, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
Future
People
(Reporter: neil, Assigned: bugzilla)
References
(Blocks 1 open bug, )
Details
Attachments
(3 files)
For some reason the above message doesn't display correctly. The problem is either: 1. Mozilla is not displaying the flowed message correctly 2. Mozilla did not post the flowed message correctly 3. David Hallowell mangled the message before posting it
Comment 1•23 years ago
|
||
Seems to wfm using build 2001101103 on Win2k.
Comment 2•23 years ago
|
||
Reporter | ||
Comment 3•23 years ago
|
||
Comment on attachment 53237 [details]
Screenshot of URL rendered with build 2001101103
My point exactly.
Doesn't seem like a bug to me either. Reporter: Before you filed this bug: Did David Hallowell explicitly tell you that he has set linelength to something less than what the message displays?
Reporter | ||
Comment 5•23 years ago
|
||
Surely linelength is irrelevant for a flowed text message?
The piece of text in questions seems flows just fine here: It resizes to the window width all the time, as it should. Is this a duplicate of bug 72601 / bug 71110?
Reporter | ||
Comment 7•23 years ago
|
||
So why does the screenshot show some of the text not resizing to the window width?
Assignee | ||
Comment 8•23 years ago
|
||
Reporter, can you save the message to file (form the mail 3Pane window, select menu edit/Save As/File) and attach it to this bug report. Thanks
Comment 9•23 years ago
|
||
I didn't do anything special, just hit reply (in Mozilla) pruned any unnecessary text and typed my reply.
Comment 10•23 years ago
|
||
Seems fine to me, looks like the only bit that doesn't flow is the quoted text, is that mean to flow like the other text with the >'s adjusted appropriately?
Assignee | ||
Comment 11•23 years ago
|
||
Comment 12•23 years ago
|
||
The quoted text already contained linebreaks, and is quoted with those, as it was originally posted. If you make the window with news://news.mozilla.org:119/3BC4F793.4050505@ukuug.org narrow enough, quoted text wraps accordingly. The position of the quote tokens (>) do not change, which isn't a bug; They still indicate the width of the lines in the original post. I can't for my bare life understand how this all even can be considered to be a bug.
Reporter | ||
Comment 13•23 years ago
|
||
Comment 14•23 years ago
|
||
in attachment 53465 [details] both the previous mailer and the one who replied used flowed
format.
It seems you are requesting that Mozilla should delete linefeeds other authors
have added in their posting? Perhaps the author wished that his linebreaks be
*exactly* as they were posted? IMO it would be very incorrect behaviour to
overrule that, thus: this bug is invalid.
Reporter | ||
Comment 15•23 years ago
|
||
OK, so the original post was flowed, and the reply was flowed, so where did the linefeeds come from? P.S. Thanks for bearing with me on this one.
Comment 16•23 years ago
|
||
The linefeeds come from the linefeeds.
In the latter case, the linefeeds a user who writes flowed manually inserted
during write.
In the former case, the mail contains the linefeeds the original author set for
where she wish automatic formatting to break lines, as well as eventual extra
linefeeds added before that "rule" triggers.
If i write a poem in mail, setting linefeed to wrap at 30 char
and then write:
Given this poem of linebreaks,
it's vital you quote it right,
for if you delete my settings,
the poem will look like shite!
Do you consider it correct behaviour if you quote it as:
> Given this poem of linebreaks, it's vital you quote it right, cuz if you
> delete my settings, the poem will look like shite!
See..If you break my settings, you loose the secret hidden in reading the first
letter of each sentence.
Reporter | ||
Comment 17•23 years ago
|
||
My understanding was that the original post contained flowed text and therefore the quote should flow as well.
Comment 18•23 years ago
|
||
i take back that poem.. I found the original message and quoted it to myself in mail with various settings: There is a problem all right.. but i see the opposite of you: I can't make things *wrap*. Replying in plain text mode doesn't work. Replying after unchecking "wrap to page width" doesn't work. Setting linewrap in compose to 30 chr. doesn't work. All looks fine while composing, but after receiving the mail, content is as wide as pagewidth, regardless of my settings. I rest my case.
Reporter | ||
Comment 19•23 years ago
|
||
news://news.mozilla.org:119/3BCCD397.30002@server.domain is a better example of what I was expecting to see.
Reporter | ||
Comment 20•23 years ago
|
||
Curioser and curioser... compare these two messages: news://news.mozilla.org:119/3BDDB8E4.4070105@ukuug.org news://news.mozilla.org:119/3BDDBE65.80101@ukuug.org One quoted properly, the other one didn't...
Assignee | ||
Updated•23 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Reporter | ||
Comment 21•22 years ago
|
||
Finally I suffered from the problem myself! Steps to reproduce problem: 1. Reply to a message (so that there is quoting) in plain text mode [or use options/format to force plain text conversion?] 2. Save the message (as draft) but keep the window open for comparison 3. Edit the draft in a new window Expected results: edited draft appears identical to saved draft window. Actual results: edited draft loses quoting information (blue colour etc.) This means that when the message is posted the >s post literally and not as a flowed quote. Additional information: the draft correctly previews the quotation. Workaround: Delete the >s, cut the quote and paste it back as quotation.
Severity: trivial → normal
Summary: Something wrong here :-( → Editing draft (or other plain text message as new) loses flowed quoting information
Reporter | ||
Comment 22•22 years ago
|
||
I think akk fixed this by changing the way the text was inserted, but it's too long ago for me to remember the duplicate bug#
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Updated•20 years ago
|
Product: MailNews → Core
Comment 23•19 years ago
|
||
I think this bug still exists (not worksforme) and should be marked a dupe of bug 155622.
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•