Closed
Bug 343262
Opened 18 years ago
Closed 18 years ago
Interface font should be sans-serif and not serif
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jlp.bugs, Assigned: masayuki)
References
Details
The interface font (for menus and things like this) used to be sans-serif. But in recent Linux nightlies it is serif, which is a lot harder to read and doesn't look as clean as sans-serif font. I've tried several nightlies to see when the change happened. In the nighlty from 2006-06-09 the interface font was OK, but in 2006-06-10 it is not OK.
Comment 1•18 years ago
|
||
A regression from bug 340590, maybe? That was supposed to be windows-only, but maybe it changed common code.
Product: Firefox → Core
QA Contact: general → general
Updated•18 years ago
|
Component: General → GFX: Thebes
QA Contact: general → thebes
Comment 2•18 years ago
|
||
*** Bug 349902 has been marked as a duplicate of this bug. ***
Comment 3•18 years ago
|
||
I think the point of this bug is that
the change of
Edit -> Perferences -> Content -> Fonts & Colors -> Default Font
is affected to the user interface (UI) font.
Once we change the "Default Font" value, the UI font of newly created windows and dialogs is shown with the "Default Font" value.
The "Default Font" preference never should be affected to the UI font.
Comment 4•18 years ago
|
||
confirmed regression range in comment 0, http://bonsai.mozilla.org/cvsquery.cgi?date=explicit&mindate=2006-06-09+04&maxdate=2006-06-10+05 and behavior described in comment 3. I get this on one machine and not the other though, which is fun :\
Comment 5•18 years ago
|
||
I tested home-made gtk2 (not cairo-gtk2) build and cannot get.
Is this the regression by bug 340590?
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2006-06-09+17%3A21&maxdate=2006-06-09+17%3A21&cvsroot=%2Fcvsroot
Comment 6•18 years ago
|
||
(In reply to comment #5)
> I tested home-made gtk2 (not cairo-gtk2) build and cannot get.
>
I can confirm that its cairo-gtk2 only and not gtk2. I filed bug 349902 (without finding this one) there I attached two screenshots.
Comment 7•18 years ago
|
||
(In reply to comment #5)
> I tested home-made gtk2 (not cairo-gtk2) build and cannot get.
>
> Is this the regression by bug 340590?
> http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2006-06-09+17%3A21&maxdate=2006-06-09+17%3A21&cvsroot=%2Fcvsroot
it probably is, there doesn't seem to be anything else relevant in the regression range -- but if you can reproduce this bug in a homebrew cairo-gtk2 build, you could verify that it is (see the "Show commands which could be used to back out these changes" link on the bonsai list (of course since that was >2mo ago, it might conflict all to hell))
Comment 8•18 years ago
|
||
As far as I tested, if the"Default font" is set to "serif", "sans-serif", or "monospace", the UI font is not changed. But if the "Default font" is set to other fonts, the UI font is changed.
Comment 9•18 years ago
|
||
(In reply to comment #8)
> As far as I tested, if the"Default font" is set to "serif", "sans-serif", or
> "monospace", the UI font is not changed. But if the "Default font" is set to
> other fonts, the UI font is changed.
>
That's right, but strange as doing this with a gtk2 only build nothing changes.
Using your comment as starting point I found that when you change in the Advanced Pane "Proportional" from the default "serif" to "sans-serif" UI uses Helvetica (or whatever you defined as sans-serif font). Again these changes had no influence on the UI fonts in gtk2 (non-cairo) or ff 2 builds.
Assignee | ||
Comment 10•18 years ago
|
||
taking this. I think that this bug is a easy mistake.
I'll create the patch after bug 339513.
Assignee: nobody → masayuki
Depends on: 339513
Assignee | ||
Comment 11•18 years ago
|
||
I added the code for fixing this bug in the patch of bug 339513.
Status: NEW → ASSIGNED
Assignee | ||
Comment 12•18 years ago
|
||
fixed by bug 339513.
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•