Comment 128 for bug 10883

(In reply to Daniel Kabs, reporting bugs since 2002 from comment #46)
> > You *cannot* switch composition format, once you're in
> > plain text compose, there is no way to switch to HTML/rich text. That's what
> > this bug is about.
> I agree. This is the "malfunction" I was talking about. The menu for
> selecting delivery format should be available always.
No, when you're already in plain text composition, you cannot send that plain text as HTML, hence no menu.

> Even if you "dumb down" the delivery format from HTML to plain
> text, the formatting toolbar is still available. At least in my version of
> TB 52.1. Just tried it. If you switch to plain text delivery format, the
> content is "dumbed down" on sending, e.g., bold text is encoded by putting
> the text in between asterisks (e.g., "*bold*")
Exactly. Then composing HTML, the formatting toolbar is always present regardless of which *delivery* format you chose. That's changed in bug 1288914. You can add bold/underline, etc. and when turning this to plain text that is converted to *bold* and _underline_. Lists are also converted.

I'd really like to bring the discussion to a close here. The bug is about a facility to "upgrade" a plain text composition to rich text. Switching from rich text to plain text is dangerous since you'd lose all your formatting and embedded images.

More comments won't get us anywhere, we need someone to implement this to move forward.