Linux (1999-11-09-11 M11) Need a way to allow users to change the font size of the thread pane and folder pane. On Linux, the font in the thread pane and folder pane is so small that may discourage users to use seamonkey.

I have a separate bug (bug 18456) for folder pane font size.

I assume this is something which should be fixed in the global skin. Reassigning to german, cc hangas. Note that I don't think we need UI to change the font in the tree widget, but the default font/size should look right on all platforms.

Agree. I do think we need some context menu UI that is not expensive to iForwarding to Paul Hangas for implementation.

*** Bug 20418 has been marked as a duplicate of this bug. ***

P4 per m/n staff mtg today

Mass move mailnews bugs to Putterman. Ouch.

Fenella - is the font size still very small?

I can barely read the text in the thread pane at all. I've hunted for where this font is defined, so that I can change it in my user.css, but haven't found it, and there really should be a way for ordinary users to get a readable font as well. (Same goes for dialogs and buttons, which is a non-mailnews-specific issue: see bug 5236.) Nominating for nsbeta2 since unreadable fonts make the product very hard to use and changing font size won't hurt stability. (I don't think UI to change the font needs to be nsbeta2, just having the default font be readable, or having someone figure out how to set it in user.css so we can offer users a workaround if they can't use the product otherwise.)

The font size is more readable now then earlier but it is still small.

Putting on [nsbeta2-] radar. Not critical to beta2.

moving to future milestone.

The font site is severly altered by changing the screen resolution. There should be a menuitem under VIEW to increase/decrease the font size of all three panes at once (like the browser already has - CTRL-+/-). I just got a new monitor and switched from 1024 (small fonts) to 1280 (large fonts) and messenger's fonts are way too small now. A VIEW - TEXTSIZE menuitem would be very helpful in letting users adjust the display to their needs (near-/farsighted people have differing viewing needs).

*** Bug 64173 has been marked as a duplicate of this bug. ***

Marking nsbeta1 and access, because the ability to change the font size will help those with poor vision.

*** Bug 64173 has been marked as a duplicate of this bug. ***

marking nsbeta1-

This is a common request in the netscape6 newsgroups, especially important for people with very low and very high resolutions to bring the text into a readable range.

*** Bug 82830 has been marked as a duplicate of this bug. ***

A partial but unsatisfactory solution in Windows: Go to Settings - Control Panel - Display - Appearance - Scheme, and select Windows Standard (Extra Large). This will increase the size of your thread pane font if you're in the Classic Theme. Unfortunately, the lines of text now bleed together in the thread pane. Clearly the line height is not correctly calculated. That makes this an important accessibility bug to be fixed for FCC Section 508 compliance. Adding fcc508 keyword.

On second look, changing the Windows font does work. It just looks funny - there's not enough space between the lines, and the highlight doesn't highlight the bottoms of letters. Removing fcc508 keyword.

reassigning to sspitzer

*** Bug 116894 has been marked as a duplicate of this bug. ***

A workarround for that problem is to use a userChrome.css file containing something like: treechildren {font-size: 110% !important;} Alternatively, if one wants to change the the thread pane only (without changing the folder pane): #threadTree {font-size: 110% !important;}

*** Bug 145631 has been marked as a duplicate of this bug. ***

*** Bug 206748 has been marked as a duplicate of this bug. ***

*** Bug 189769 has been marked as a duplicate of this bug. ***

Where does the userchrome.css file go? I do not see one on my system anywhere.

The page you linked to in the bug you filed that was duped to this explains about userChrome.css.

I.e., look at http://bugzilla.mozilla.org/show_bug.cgi?id=206748 to read about the work around using userChrome.css.

*** Bug 225415 has been marked as a duplicate of this bug. ***

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420

The font and its size in the default theme are taken from the system. Given that bug 18456 is also WONTFIX, we're not going to fix anything here.

Extension fodder -> Use Stylish instead.