Comment 127 for bug 10883

Revision history for this message
In , Bugzilla-kabsi (bugzilla-kabsi) wrote :

(In reply to Jorg K (GMT+2) from comment #44)
> Please don't confuse switching *delivery* format with switching
> *composition* format.

I didn't. To the best of my knowledge there is no UI element that allows a user to directly switch composition mode in TB. There's however the account setting parameter "Compose messages in HTML format". With this parameter set, a new compose window sports a rich text formatting toolbar and the menu "Options > Delivery Format" is available.

> 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.

> If you're in HTML compose, you can "dumb" the delivery
> format down to plain text. You can easily tell the difference by checking
> whether the formatting toolbar is available.

I disagree. 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*")

Regarding a draft created by iPhone, I'll have to check.

And yes, I know how to configure TB functions - at least since 2002. ;-)