HTML signature is broken if sender email is changed from plain text to HTML
Categories
(Thunderbird :: Untriaged, defect)
Tracking
(Not tracked)
People
(Reporter: marcel.fontes, Unassigned)
Details
(Whiteboard: [closeme 2020-12-15])
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.122 Safari/537.36
Steps to reproduce:
I have two (or more) email accounts.
The settings of account A is: "send emails as plain text".
The settings of account B is: "send email as HTML".
The email signature of A is plain text.
The email signature of B is HTML.
-
I want to send a new email. In my accounts list, account B is highlighted (marked blue). I click on "new email". A window opens and I can see the working HTML signature. Everything is fine.
-
I want to send a new email. In my accounts list, account A is highlighted (marked blue). I click on "new email". A window opens and I can see the working plain text signature. Everything is fine.
-
I want to send a new email. In my accounts list, account A is highlighted (marked blue). I click on "new email". A window opens and I can see the working plain text signature. So far so good.
But now, I change the sender adresss/account in the dropdown list from A to B.
Actual results:
The email signature changed from A to B. But the signature kept as plain text.
Expected results:
I expected a change from the plain text signature to a HTML signature.
I did not test, if the whole email is not sendend as HTML.
Comment 1•6 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (non,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)
Comment 2•5 years ago
|
||
Reporter,
How does it behave when using version 78?
(In reply to Wayne Mery (:wsmwk) from comment #2)
Reporter,
How does it behave when using version 78?
In v78 everything is fine.
Description
•