Closed
Bug 651545
Opened 14 years ago
Closed 14 years ago
Signature not in correct spot
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: sdhomz, Unassigned)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; GoogleT5; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 3.0.30618; InfoPath.2; Media Center PC 5.0; SLCC1; Tablet PC 2.0; .NET4.0C)
Build Identifier: Thunderbird 3.1.9
When doing a reply to an email and using signatures, the chosen signature cannot be placed underneath my reply. It is instead placed at the very bottom of the quote or end of email. I have the settings at "Start my reply above the quote" and "place my signature below my reply".
Other than this issue, it's been great and thanks for putting this together!
Thanks,
Alex
Reproducible: Always
Steps to Reproduce:
1. Reply to an email.
2. Choose a signature to be used.
3.
Actual Results:
It places the signature at the very bottom of the email, after the quote or original email.
Expected Results:
Place the signature after my reply, above the quote.
Do you have multiple accounts or multiple identities for an account?
That setting is per identity, thus find the "Manage Identities" button in the main Account Settings page and check for all listed identites (Edit button)
that the setting is as intended.
Also, add-ons sometimes interfere with signatures, do you have anything listed in Tools > Add-ons > Extensions?
Component: General → Message Compose Window
QA Contact: general → message-compose
I do have multiple accounts but not multiple identities for each account. I am actually referring to the Signature Switch add-on to utilize different signatures and didn't use the default signature area for placing my signature. After having done this, it works!
Thanks so much!
Alex
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Thanks for confirming. I'm changing the resolution to "Invalid" though as it was a 3rd-party issue caused by the add-on ("Fixed" is used only when a bug was actually identified and changes made in the code).
Resolution: FIXED → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•