Closed
Bug 33641
Opened 25 years ago
Closed 23 years ago
Make dependency between fonts and charsets clear in UI
Categories
(SeaMonkey :: Preferences, defect, P3)
SeaMonkey
Preferences
Tracking
(Not tracked)
VERIFIED
FIXED
Future
People
(Reporter: BenB, Assigned: bugs)
References
(Blocks 1 open bug)
Details
(Keywords: helpwanted, Whiteboard: [nsbeta3-])
Most font settings depend on a charset, e.g I change the font for a font family
/and/ charset. This is not clear in the UI. E.g. currently, I can't tell from
the UI, if "Default font" applies to all charsets or only the current one.
The logic should be visible by the UI organization. If possible, you could use
a group with the charset selecting widget as title.
While fixing this, please also vertically center the variable width font size
widget between serif and sans-serif font selectors to make clear, that it
applies to both.
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → M16
Assignee | ||
Comment 2•25 years ago
|
||
I have redone the infrastructure behind this preferences panel, however the
layout of the content is still open to change. Currently it takes up slightly
too much vertical space. Suggestions for layout improvements are welcome!
Reporter | ||
Comment 3•25 years ago
|
||
> If possible, you could use
> a group with the charset selecting widget as title.
This could look like this (please excuse the ascii-art):
+-------------------------+-+
+-| Western |V|-------------------------+
| +-------------------------+-+ |
| |
| +---------------------+-+ |
| Sans-Serif Font: | Helvetica |V| |
| +---------------------+-+ |
[...]
+-------------------------------------------------------+
Comment 4•25 years ago
|
||
Thanks to Ben, the layout of the font prefs UI is already much improved. I did
at one point try to put the language menu into the title of the titledbox, but
the menu itself came up in a strange place (too low). Ben, what do you think?
Assignee: erik → ben
Status: ASSIGNED → NEW
Updated•25 years ago
|
Target Milestone: M16 → M17
Assignee | ||
Comment 5•25 years ago
|
||
seems like a good extra idea if it would actually work. I think the distinction
is now clear however. closing the bug.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 6•24 years ago
|
||
looks better, yes. verif using 2000.05.18.08 [opt comm] on linux, mac and winnt.
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 7•24 years ago
|
||
No, this is not at all fixed. In fact, it got worse. REOPENing.
You should be able to infer the semantics just from looking at the dialog.
Currently, if you do that, you will come to wrong results.
E.g. Fixed and variable width fonts depend on the charset. The serif/sans-serif
preference is located in the middle of them, but does *not* depend on the
charset. To know for sure, you have to
- Remember the charset and serif/sans-serif setting
- Change the charset
- Change the serif/sans-serif preference
- Change back to the old charset and see, if the serif/sans-serif setting
changed
Bad.
If you can't use the drop-down as title of the group, then move it directly
above the title. Exactly those prefs (i.e. none else) depending on the charset
should be in the group.
An alternative would be to use a list (a grip in XUL terms, I think), but I
don't know, if that is a good idea.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Comment 10•24 years ago
|
||
See <http://critique.net.nz/project/mozilla/prefs/tardis/#std-display-fonts>, and
also bug 28899 (where German approved that spec).
The spec replaces the serif/sans-serif radio buttons with a separate `Normal'
setting, like IE 5/Mac, in case your favorite font (for cases where the font
family isn't specified) isn't the same as your favorite font for a particular
font family (for example if it doesn't really fit into any of the categories). If
you can't implement this in time, give the popup menu items `Serif', `Sans
serif', `Monospace', etc.
The spec also includes a `Use default choices for this encoding' checkbox, which
(a) helps prevent you being confused by the encodings if all you want to do is
change the fonts, and (b) saves you from having to change the fonts for every
single encoding if you decide you like Verdana better than Times.
If it's not possible to have a popup menu (or a checkbox, or a radio button) as
the title for a titledbox, file a separate XPToolkit bug for that, and for now
put the menu above the group.
Comment 11•24 years ago
|
||
nav triage team:
seems to work as well or better then 4.x, so marking nsbeta3- (trying to ship
on time). However, it would be nice to improve, so adding keyword helpwanted to
encourage people on the net to offer a fix. M Future.
Comment 12•23 years ago
|
||
I would say the new fonts prefs panel makes this as clear as it's going to get.
BenB, it's your bug - is it OK to close this one?
Gerv
Assignee | ||
Updated•23 years ago
|
Status: REOPENED → ASSIGNED
Comment 13•23 years ago
|
||
The reporter of this bug wrote in bug 28899 comment 48: `The new layout looks
so much cleaner and is more correct, that I wonder why it hasn't always been
this way'. Marking fixed.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 23 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•