Open Bug 186197 Opened 23 years ago Updated 17 years ago

Selecting fonts for multiple characters sets too tedious

Categories

(SeaMonkey :: Preferences, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

People

(Reporter: mozilla, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021210 Debian/1.2.1-3 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021210 Debian/1.2.1-3 There are about 7 character sets in the font selection list that can use regular iso10646-1 fonts, and most users will probably want each of those character sets to use the same fonts and font sizes by default. The way Mozilla's font preference dialog is designed those fonts must be selected individually for each character set. I timed myself and setting all the fonts and sizes for one character set takes 50 seconds. That is over 5 minutes just to set the default fonts for sililar character sets. This bug is about designing a new user interface (UI) for selecting fonts that is more efficent than the current design. I will propose a suggestion. 1.) Have a "Default Fonts" character set in the dropdown menu. Fonts and sizes set there will apply to all possible character sets (with the encoding part of the font different of course) that do not have explicit values set. Then there will be a new font in the dropdown menu for each style called "Use Default"; it will appear at the top of the list and be the default selection. Reproducible: Always Steps to Reproduce:
Severity: minor → enhancement
Priority: -- → P2
This isn't layout. Moving to Preferences.
Assignee: core.layout.fonts-and-text → prefs
Component: Layout: Fonts and Text → Preferences
QA Contact: ian
Assignee: prefs → neil.parkwaycc.co.uk
OS: Linux → All
Hardware: PC → All
Product: Browser → Seamonkey
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/
confirming bug
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee: neil → nobody
Priority: P2 → --
QA Contact: prefs
You need to log in before you can comment on or make changes to this bug.