Closed Bug 294665 Opened 20 years ago Closed 19 years ago

RFE: Default HTML Options should enable setting default style

Categories

(Thunderbird :: Preferences, defect)

All
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: kilianh, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (compatible; Konqueror/3.3; Linux 2.6.11-gentoo-r4) (KHTML, like Gecko)
Build Identifier: Thunderbird version 1.0.2 (20050511)

I'd like to compose ALL my messages in HTML with 'Paragraph' Style and Times  
New Roman as the font to standardise my communication.  
The Preferences -> Composition -> HTML Options allows for setting the font,  
size and colour only, but not the style. Consequently, whenever I compose a new  
email, the font is correct but the style defaults to Body Text which I don't  
want. To make matters worse, when I then change to 'Paragraph' from the 
drop-down menu manually the font changes back to variable width 

Reproducible: Always

Steps to Reproduce:
1.Go to HTML Options as described above and try to change default style 
   
Actual Results:  
see above 

Expected Results:  
The HTML Options dialogue should have an additional widget allowing the user to 
choose the default style for all HTML messages 

I don't know if this qualifies as a bug report(font change with style change) 
or an RFE because the former problem might just be a feature. 
It basically all comes down to not being able to edit HTML messages by default 
the way I want them to. 
Also, note that the reason I want 'Paragraph' style is to be able to hit 
<enter> to start a new paragraph (<p>) and not line (<br>), which is what bug 
#92686 addresses (hopefully this will be fixed by the next Thunderbird 
release?). At the moment I need to select 'Paragraph', then 'Times New Roman', 
then whenever I want <p> press <enter> twice, far from optimal.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.