Clicking mailto: "Compose message to" always opens new HTML compose window
Categories
(Thunderbird :: Untriaged, defect)
Tracking
(Not tracked)
People
(Reporter: klaus.kusche, Unassigned)
Details
Steps to reproduce:
TB Version 128.4.0esr:
I right-clicked a "mailto:" link in a HTML mail body or a mail adress in a plain text mail body and selected "Compose message to".
Actual results:
A compose message window opened in HTML compose mode,
although the account is set to plain text only.
Expected results:
The compose window should have been opened in plain text mode.
All other ways to open a compose window for that account
(e.g. "write" or "reply") open a plain text compose window, as they should.
Right-clicking on a mail address in the mail header (not body)
and selecting "Compose message to" also opens a plain text compose window,
only mail addresses in the mail body have this problem.
|
||
Comment 1•9 months ago
|
||
(Maybe bug 550414)
|
Reporter | |
Comment 2•9 months ago
|
||
Quite likely not the same problem, just because of the age of the other bug.
I'm not sure when exactly I observed this problem for the first time,
but I use the "Compose message to" feature regularly,
and I think it behaved correctly in the past?
Moreover, according to bug 1911596 and bug 1914250,
that part of the code might have been changed recently?
|
|
||
Comment 3•9 months ago
|
||
It seems it at least used to work (bug 1737637)
Code should be around https://searchfox.org/comm-central/rev/59f3615b36c5ce10b1458e03aa5d68dae0e45d60/mail/actors/MailLinkParent.sys.mjs#56
|
|
Reporter | |
Comment 4•9 months ago
|
||
I have two accounts.
One is set to "compose HTML" and "always send plain+HTML".
The other is "compose plain" and "send plain".
I don't know which one is the first and which one is the second.
When clicking mailto: links, TB fills in the correct "From:" and the correct signature,
so it distinguishes correctly between the two accounts,
but it opens HTML compose in both cases.
|
||
Comment 5•9 months ago
|
||
This indeed seems to be the problem to be fixed in bug 550414.
Description
•