59182 - Should we stop recommend plain text when writing html lists?

Status: VERIFIED WONTFIX

(SeaMonkey :: MailNews: Message Display, defect, P3)

Description

[Daniel Bratell]

After seeing bug 59181 I don't think it's right to recommend sending with plain
text when the text contains html lists. I now BenB has worked on this before so
I assign it to you since I don't know who else could be responsible for this area.

Comment 1

[Ben Bucksch (:BenB)]

After you made the lines fixed, all "damage" done by sending as plaintext is the
lost flowing information. That's the same 4.x does for *all* lines, without even
bothering to ask. -> No reason to suggest HTML. WONTFIX. Hope you don't mind.

Comment 2

[Daniel Bratell]

I've not used NS4.x's composing. Does it really recommend you to send as plain 
text when the sender has used html lists?

Anyway, I think we should aim on being better than NS4.x and what's wrong with 
sending multipart/alternative anyway? The extra disk and network space needed is 
quite negligable compared to the size of all the binaries out there.

Comment 3

[Ben Bucksch (:BenB)]

> Does it really recommend you to send as plain 
> text when the sender has used html lists?

No, it doesn't. But it looses flowing info without even asking. We are so nice
to at least ask (personally, I find that unnecessary - I'd send lists as
plaintext without asking).

> Anyway, I think we should aim on being better than NS4.x

We are a *lot* better, thanks to your and mine contributions.

> what's wrong with sending multipart/alternative anyway?

Please, don't start that one again. It's evil(TM). See the "plaintext vs. HTML"
thread on .mail-news for details.

Comment 4

[[e-mail] (gone - use [e-mail] instead)]

VERIFIED WON'T FIX to get off radar and per comments in the bug.