Closed Bug 17000 Opened 25 years ago Closed 25 years ago

Set html/text for compose when no folder/acct is selected

Categories

(MailNews Core :: Backend, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 15238

People

(Reporter: laurel, Assigned: sspitzer)

Details

In current builds, when you launch a compose window in Messenger without having an account selected in the folder pane, the compose window always opens in plain text format regardless of the html pref settings for your accounts. I would think we might want to set this to track to a default account, wherein if that account's pref is set for html compose, that's what we open as a default. We should decide the proper behavior for launching compose window when no account is selected. I would also like to know if launching compose from the browser window would follow the same decision (to track to a default account). Steps to reproduce: 1. Launch to messenger. Set the first or all of your accounts to use an html compose window -- Edit|Account Setup|<select account>|"compose messages using html". Confirm OK. 2. Select a folder within one of the accounts and click New Msg to verify the html setting is truly activated. Close the compose window. 3. Collapse the account hierarchy or close and relaunch messenger so you will window up having no account selected. (the behavior in selection upon collapsing account hierarchy differs among platforms) 4. Having no account selected in the folder pane/sidebar, click New Msg. Result: compose window launches to a (default) plaintext window, although all my accounts are set to use html. Found while using 1999-10-21 am commercial builds on mac, linux and NT.
QA Contact: lchiang → laurel
I think that momoi filed a bug on this already (or something similar)
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Yes, there is a bug already. Doh. *** This bug has been marked as a duplicate of 15238 ***
Status: RESOLVED → VERIFIED
:-)
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.