User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 My default mail format for my account is "plain text". I have created a new mail identity so that I can write HTML messages and use an HTML signature when I desire. When I switch to the identity in the compose window, it places my HTML signature in the compose window, but the signature is in plain text. There is no way for me to compose HTML messages unless I enable it for the account globally from the Account settings (Tools->Account Settings->Composition & Addressing). Another way to describe this problem is that switching between a "Plain Text" identity and an "HTML" identity does not work as expected. Reproducible: Always Steps to Reproduce: 1. Tools->Account Settings...->Composition & Addressing. De-select "Compose Messages in HTML Format" 2. Tools->Account Settings...->(Click on the account root on the left)->Manage Identities. 3. Create a new identity. Click on the "Composition & Addressing" tab. Select "Compose Messages in HTML Format" 4. Click OK, OK, OK. 5. Click the "Write" button to compose a new message. Your default identity for the account will be active (Plain Text). 6. Click the "From:" pulldown menu and select your newly created identity. Actual Results: The mail compose window stays in plain text mode after switching to the HTML enabled identity. Expected Results: The mail compose window should switch to HTML composition mode. Should have options for font, color, etc.

I thought we had a bug for this particular issue, but I can't find it at the moment. This is similar to bug 136212. This one, however, requires some means of changing the compose window, which is not currently feasible; adding a dependency for that. The workaround is: if you know ahead of time that you're going to want to compose in HTML, hold down the shift while clicking the Write, Reply or Forward buttons, then change the identity -- if in fact a separate identity is still desirable, given the workaround. (Note that Forward Inline does not correctly switch modes.) See also bug 218346, bug 270681.

(In reply to comment #1) > I thought we had a bug for this particular issue, but I can't find it at the > moment. This is similar to bug 136212. I don't see a dup either. Perhaps you were thinking of Bug 275804 Confirming.

*** This bug has been marked as a duplicate of 275804 ***