Open
Bug 223983
Opened 21 years ago
Updated 2 years ago
Maintain quote status for manually-prefixed broken quote lines (flowed)
Categories
(MailNews Core :: Composition, defect)
MailNews Core
Composition
Tracking
(Not tracked)
NEW
People
(Reporter: mcow, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
This is a subset of the problem in bug 161968, that applies only for
format=flowed composition. If that bug is fixed, this bug should be moot.
Situation: composing a reply, split a quote (type Enter in the middle of a
quoted line). In the new blank line where the cursor exists, typed text is
"normal" rather than "mailcite". The mailcite line following the cursor does
not have a leading ">" (bug 161968). User types her interspersed comment, then
types ">", then types Del to join the ">" with the subsequent quote. That quote
still appears in blue, but the ">" is in black (easy to miss).
Actual results:
On transmitting the message, the entire line is treated as "normal" and (for
flowed text) is space-stuffed, losing its quote status on receipt.
Expected results:
Mozilla recognizes that the line is primarily a mailcite, extends the
mailcite-span back to include the ">" prefix, and transmits it without
space-stuffing.
Workarounds:
1) Instead of typing the ">" into the blank area, move the cursor to the
beginning of the split-quote line. Typing the ">" at that point includes it in
the mailcite, and the line is handled as expected.
2) Select the combined normal-">" plus mailcite text line, and Rewrap. This
will recharacterize the line as a quote. (But see bug 220575.)
For text that is not sent as f=f, there is no space stuffing, and the received
message displays the line as a quote.
Updated•20 years ago
|
Product: MailNews → Core
Comment 1•18 years ago
|
||
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
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•