Closed
Bug 44552
Opened 24 years ago
Closed 24 years ago
Finetune Intelligent Send
Categories
(MailNews Core :: Composition, defect, P3)
MailNews Core
Composition
Tracking
(Not tracked)
VERIFIED
FIXED
M18
People
(Reporter: BenB, Assigned: BenB)
Details
Attachments
(1 file)
18.23 KB,
patch
|
Details | Diff | Splinter Review |
We need to take care that we don't trigger the askSendFormat dialog too often.
2 cases are known:
1. We reply to a HTML msg containing a <div> or <span> that just includes
optional XML-like information using the |class| attribute.
2. We reply to a HTML msg that in turn replies to a plaintext msg and is sent by
a Mozilla, i.e. the quote part contains tags inserted by our recognizer. (The
"Send structs as styles" stuff is done after intelligent send, that's why you
need such complicated circumstances to see the problem.)
I consider the first one being quite severe, as it propably means that we cannot
send out <div>s as long as those Mozillas are in large use. But <div>s are cool.
Assignee | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•24 years ago
|
||
3. Reply to format=flowed (or any plaintext?) mails.
Assignee | ||
Comment 2•24 years ago
|
||
Also, honor the pref for outputting structs.
Assignee | ||
Updated•24 years ago
|
Target Milestone: --- → M18
Assignee | ||
Comment 3•24 years ago
|
||
> 3. Reply to format=flowed (or any plaintext?) mails.
Has been resolved by another bug.
2. Isn't that bad anymore, because the "recognize structs during send" pref is
disabled by default and removed from the prefs UI.
1. remains. I'll propably just check for a style atribute, and if none exists,
ignore the span/div.
Assignee | ||
Comment 4•24 years ago
|
||
> 2. Isn't that bad anymore, because the "recognize structs during send" pref is
> disabled by default and removed from the prefs UI.
That's why I decided not to check for these tags, for perf reasons. However, I
forgot the <a> stuff, which wasn't always recognized (e.g. email addresses). I
changed that.
Ignoring simple <div>s/<span>s and honoring the structs pref is also fixed.
Will attach patch. It will also contain a part of the fix for bug 52042.
ducarroz, please review.
Keywords: review
Assignee | ||
Comment 5•24 years ago
|
||
Comment 6•24 years ago
|
||
looks good. R=ducarroz
Assignee | ||
Comment 7•24 years ago
|
||
Patch checked in. Mamrking FIXED. Please file new bugs, if you have other
suggestions for tuning.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 9•24 years ago
|
||
fenella,
2. and 3. above are propably not very important in practice, at least not yet.
You can verify 1. by manually creating an HTML msg containing a "<div
class=hello>This is a div with an arbitary class</div>" in the source.
As for the structs pref, en/disable pref "converter.html2txt.structs", make sure
you have the format pref to "ask" and send yourself a msg with (only) bold text.
Pref enabled: The askSendFormat comes up, telling you that it can convert the
msg to plaintext without losing info. Pref disabled: The dialog tells you that
it will not convert the formatting.
Assignee | ||
Comment 10•24 years ago
|
||
> You can verify 1. by manually creating an HTML msg containing a "<div
> class=hello>This is a div with an arbitary class</div>" in the source.
..adn then reply to it. If there only that <div> as non-trivial formatting, the
askSendFormat dialog shouldn't come up.
Comment 11•24 years ago
|
||
Mac (2000-09-26-04 M18)
Linux (2000-09-26-06 M18)
Mac (2000-09-26-04 M18)
Verifying 1 works on on all platforms.
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: MailNews → Core
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
•