Since TB 52, problems with text rewrap (Ctrl+R) and mail.compose.wrap_to_window_width
Categories
(Thunderbird :: Message Compose Window, enhancement)
Tracking
(Not tracked)
People
(Reporter: kirk.wonder, Unassigned)
References
Details
Attachments
(7 files)
Sreenshot of inserted (unformatted) text by window width in TB 45.8.0
+++ This bug was initially created as a clone of Bug #1661957 +++
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4250.0 Iron Safari/537.36
Steps to reproduce:
Up to and including version 45.8.0, TB wrapped inserted (unformatted) text by window width if "mail.compose.wrap_to_window_width" was set to "true" (see TB 45.8.0 - Ctrl V.png). If you then edited this inserted text with "Rewrap" resp. Ctrl R, TB wrapped the text correctly to line length 72 characters (default) ( see TB 45.8.0 - Ctrl R.png).
Actual results:
Since version 52.x.x this behavior has changed. Despite setting "mail.compose.wrap_to_window_width" to "true", TB 52.9.1 wraps the text to about 90 characters per line (see TB 52.9.1 - Ctrl V.png) or TB 68.12.0 wraps the text to 72 characters per line (TB 68.12.0 - Ctrl V.png).
It becomes annoying when the inserted text is rewrapped (Ctrl R). Quotations are generally no longer wrapped correctly (see TB 52.9.1 - Ctrl R.png), "normal" text is wrapped unattractive in TB 68.12.0 (see TB 68.12.0 - Ctrl R.png).
Expected results:
Furthermore, inserted (unformatted) text should be wrapped according to window width if "mail.compose.wrap_to_window_width" is set to "true". Furthermore, this inserted text should be wrapped correctly, so that "normal" text and quotations appear in the set line length.
|
||
Comment 2•5 years ago
|
||
Reporter (Ransom), could you please unpack your screenshots from the zip file and attach them as individual files to this bug, each with description? Any particular reason why you are blocking needinfo requests on a virgin BMO profile? We often use needinfo to ask questions to reporters and make sure we get your attention.
Thomas D., I accidentally made wrong settings in my General Preferences. In the meantime I have set this back to default.
Originally I wanted to upload the screenshots as single files, but that didn’t work resp. it was only possible to upload one file. If you explain to me how this works, I will gladly upload the files individually. But it’s not necessary to write descriptions for the pictures again, because it is the other way round: In the error description the screenshots (in brackets) are assigned to the description.
|
|
||
Comment 4•5 years ago
|
||
(In reply to Ransom from comment #3)
Thomas D., I accidentally made wrong settings in my General Preferences. In the meantime I have set this back to default.
Great, thanks.
Originally I wanted to upload the screenshots as single files, but that didn’t work resp. it was only possible to upload one file. If you explain to me how this works, I will gladly upload the files individually.
Oh, I see, yes, at the time of filing the bug, you can only add one. Pls use Attach New File button on top of your comment 0 to upload them one file at a time.
But it’s not necessary to write descriptions for the pictures again, because it is the other way round: In the error description the screenshots (in brackets) are assigned to the description.
Yeah. Ideally, description to have "Screenshot 1: ..., Screenshot 2: ... etc." then in comments you can also refer to screenshot numbers (and/or their attachment number, "attachment xxxxx" will be auto-linkified).
|
Reporter | |
Comment 10•5 years ago
|
||
|
|
||
Updated•5 years ago
|
|
|
Reporter | |
Comment 11•5 years ago
|
||
Thomas D.,
you have summarized that absolutely right.
|
|
Reporter | |
Comment 12•5 years ago
|
||
Hi folks,
Isn’t there anyone who would have joyfulness to be the proper person to work on this bug?
(Typical eMail services like Google, Yahoo! Outlook, AOL, AT&T, Verizon, BT etc. will soon only allow OAuth2 for POP3. Since this procedure is only implemented starting with TB 68.5.0, I would be happy if this bug would be fixed here relatively soon, since I’m currently only using TB 45.8.0 because of the bug mentioned here).
Description
•