Open
Bug 509316
Opened 15 years ago
Updated 2 years ago
Switching/toggling Delivery Format from HTML to plaintext does not change composition editor to default plain-text behaviors (expected: fixed text wrap/linebreak, fixed/monospaced font)
Categories
(Thunderbird :: Message Compose Window, defect)
Thunderbird
Message Compose Window
Tracking
(Not tracked)
NEW
People
(Reporter: alepulver, Unassigned)
References
(Blocks 2 open bugs)
Details
User-Agent: Opera/9.64 (Windows NT 6.0; U; en) Presto/2.1.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3
When composing or replying a message, if the composer window starts in HTML mode and you want to write a plain text message, when using Options->Format->Plain text only the HTML bar disappears but the font isn't switched to monospace and also there is no word wrap (even after installing an extension to enable/disable word wrap with a menu item, that menu item appears greyed out).
Reproducible: Always
Steps to Reproduce:
1. Set preferences to compose in HTML format.
2. Create a new message (the HTML bar shows).
3. Now you want to write a plain text message, so you select Options->Format->Plain text.
Actual Results:
The HTML bar disappears but there is no word wrap and the font is not monospace.
Expected Results:
If you reply to a plain text message or set preferences to compose in plain text, you see the text correctly word wrapped and in monospace font (which is the wait it would appear when most people read plain text mails).
There is also no way to switch to HTML composition when in plain text mode (if entered directly, without manual selection).
Comment 1•15 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4pre) Gecko/20090915 Thunderbird/3.0b4
Confirmed and changed title to "switching/toggling from html to plaintext compose doesn't change to default plain-text behaviors (no fixed text wrap/linebreak, non-fixed font/no monospace)"
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: No word wrap and monospace font when manually to plain text → switching/toggling from html to plaintext compose doesn't change to default plain-text behaviors (no fixed text wrap/linebreak, non-fixed font/no monospace)
Duplicate of bug 216132 comment 2 (or bug 339887)?
Comment 3•13 years ago
|
||
(Note: This is a follow-on from a discussion over lunch at the All-Hands)
See also possible dup/partial-dup bug 470062
This bug causes major pain editing messages for mailing lists, since the convention is that you post to IETF/etc lists in plain text. I have to manually change to plain-text (even though the list address is marked in the addressbook as wanting plain-text), and even then unless I manually select all and switch to preformat before changing to plaintext, I'm left editing using a variable-width font and changebars (instead of fixed-width and '>', which is used when editing news articles).
The change-bars are especially egregious, because I can't predict when editing if I'll get a blank line or not after them. I usually will get one blank line if I leave two blank lines in the source - but that's a different bug. I also (because I can't see what it's going to do to my text when I send) end up having to hand-wrap (and hand-rewrap) all the text.
I've just about given up on Thunderbird for mailing lists because of this.
Side issue that would help immensely to "stopgap" this issue - if there were an extension like "It's All Text" for Thunderbird that would let me edit in my preferred editor. It's mildly annoying on the web not to have your preferred editor keybindings, but it's HUGELY annoying in email.
Updated•12 years ago
|
OS: Windows Vista → All
Hardware: x86_64 → All
Updated•11 years ago
|
Blocks: delivery-format-ux
Summary: switching/toggling from html to plaintext compose doesn't change to default plain-text behaviors (no fixed text wrap/linebreak, non-fixed font/no monospace) → Switching/toggling Delivery Format from HTML to plaintext does not change composition editor to default plain-text behaviors (expected: fixed text wrap/linebreak, fixed/monospaced font)
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•