374385 - mailto: Cannot format message body in Compose Windows

Status: RESOLVED WORKSFORME

(Thunderbird :: Message Compose Window, defect)

Description

[Walter Ring]

User-Agent:       Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1; .NET CLR 3.0.04506.30)
Build Identifier: version 1.5.0.10 (20070221)

When composing new mail via a mailto: link, I cannot format my message body. The format bar is greyed out, and my font defaults to something, but not Arial (which is my default font). 

If I compose a new mail by clicking the "Write" button, everythings works fine. 

Reproducible: Always

Steps to Reproduce:
1. Click on any mailto: link or enter mailto:[e-mail]

Actual Results:  
Format bar is greyed out, cannot format my mail

Expected Results:  
Format bar should be accessible, mail should be able to be formatted

Comment 1

[Mike Cowperthwaite]

(In reply to comment #0)
> Actual Results:  
> Format bar is greyed out, cannot format my mail

Greyed out, but the bar is visible?  Are there any other problems with the compose window?  In particular, do the address fields display normally?  And are the correctly initialized per the mailto: link's address?

Do you see a similar problem with Reply?

Do you have any extensions installed?  If so, does the problem persist when you run Thunderbird in Safe Mode?

Comment 2

[Walter Ring]

Hmmm, strangely, suddenly the problem has gone. I am unable to reproduce the problem any more.

Yes, the bar was visible, but was greyed out. I could not see any other problems with the compose window. The address fields displayed normally and showed the correct mailto: address. The compose window showed Times font instead of my default Arial and could not be changed.

There were no problems with reply.

Extensions installed:
Talkback 1.5.0.10
SmartSave 0.1.3
BlunderDelay 0.5.1
MagicSLR 1.2.2

But since I am currently unable to reproduce the problem I cannot track it down further.

Comment 3

[Mike Cowperthwaite]

OK, marking WFM for now.  If the problem recurs, feel free to reopen the bug.