Closed Bug 565110 Opened 14 years ago Closed 14 years ago

When Replying, Signature Placed In Wrong Part of Message When Reply Set to Top of Message

Categories

(Thunderbird :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 278453

People

(Reporter: jeffb, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.2) Gecko/20100316 Firefox/3.6.2
Build Identifier: version 2.0.0.24 (20100228)

Assume, under Default Identity:
1.  Under Default Identity, Attach This Signature set to a default signature
    file.

2.  Under "Manage Identities"  a second signature is present, Attach This 
    Signature is set to a second signature file.

3.  Under Composition and Addressing, "Automatically quote the original message
    when replying" is checked and the options set are:

    o "Start my reply ABOVE the quote"; and
    o "Place my signature below my reply (above the quote)"

Reproducible: Always

Steps to Reproduce:
1.  With the above options set, press Reply for the message you are going to
    reply to, using the default signature file.  Behavior is correct:  new 
    message is started above the quote, signature is placed below the reply.

2.  With the above options set, press Reply, and then change the signature 
    listbox to the non-default signature.
3.
Actual Results:  
After completing step 2 above, the non-default signature appears at the bottom of the message, below the quote.  The cursor, however, is where it should be--above the quote.

Expected Results:  
With the above options set, the alternate signature should be placed below the reply (at the top of the message).  That is, the behavior should be exactly as if the default signature was chosen.
This is fixed in Thunderbird 3.0, thus I'm closing this as a duplicate.
If you can still reproduce it in 3.0.4 or the upcoming 3.0.5, please reopen
with further information.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.