Chromes on the Mac should use Geneva, not Helvetica



19 years ago
10 years ago


(Reporter: Pierre Saslawsky, Assigned: Ben Goodger (use ben at mozilla dot org for email))



Mac System 8.5

Firefox Tracking Flags

(Not tracked)




19 years ago
Waiting for bug 3371 and bug 16729 to be fixed, would it be possible to have the 
chromes on the Mac displayed in Geneva instead of Helvetica? All the Mac 
applications use Geneva.

Comment 1

19 years ago
CCd shuang. Reassigned to ben who owns the UI.
Assignee: shuang → ben
Keywords: pp
not a priority, pushing out as far as possible.
Target Milestone: --- → M20

Comment 3

19 years ago
*** Bug 33180 has been marked as a duplicate of this bug. ***

Comment 4

19 years ago
From bug 33180:
| The Mozilla UI on Mac looks *vastly* better if, in
| chrome/global/skin/default/global.css, the font-family property for `window' is 
| changed from
|   3mm Arial,Helvetica,sans-serif;
| to
|   font: 10px Geneva,sans-serif;
| Menus look much better, dialogs look much better, and the UI as a whole looks
| decidedly more Mac-like. There are a few minor side effects -- the Open Windows 
| button needs to be widened (or fixed so that its width is dynamic), and some
| lines of text in prefs panels are shown not to wrap properly with the slightly
| wider text. But these could probably be fixed quite quickly.
| I strongly suggest this crude hack be implemented as a temporary measure until 
| 3371 and 16729 are fixed, as it will curb some (not all, but some) of the wrath 
| vented by Mac users when they try Netscape beta 1.

I'm removing the milestone from this, as Ben seems not to have realized what this 
bug is for. The point of this bug is not to be implemented eventually; the point 
is for it to be implemented *now*, temporarily for beta, while we're waiting for 
3371 and 16729 -- so that Mac users find the beta more palatable than they 
otherwise would.
Target Milestone: M20 → ---

Comment 5

19 years ago
3371 is fixed. This bug is now blocked by bug 16729.
Depends on: 16729

Comment 6

19 years ago
I'm afraid it's too late for the beta even if you do the job this week-end. You 
can still try, based on what you saw in bug 33180, and I'll certainly push in 
that direction if you come up with some Geneva chromes but it will be really 
difficult to get the approval to check it in on the beta branch.

I thought about blaming Ben for the situation because he's not really a Mac guy 
and that made him an excellent scapegoat but I realized it would be extremely 
unfair: we should have done it within the Mac team several months ago already. On 
the up side, the ugly helvetica look makes it very clear that it's still a 
product in the works... And in a couple of months, they will all have such a nice 
surprise when they see beta2 with Aqua or Aphrodite.

Comment 7

19 years ago
In that case, this bug should probably be WONTFIXed, since it was intended just 
for beta, and since in the long term a superior solution (using the actual system 
font, whether it is Geneva or something else) will happen automatically as Ben 
goes through the chrome fixing bug 16729.

Comment 8

19 years ago
Correct: if Ben promises to fix bug 16729 for beta2, we can close this one as 
pierre, I tried using system fonts on Mac using a recent (2 day old - after 
your system font checkin) mozilla build and found that they didn't work ;) I'm 
using MacOS8.6...

IE5/Mac managed to do them though, so I assume I have a version of MacOS capable 
of providing this information... 

Comment 10

19 years ago
ben, it works for me. To verify:
- Open the Appearance Control Panel
- Under the Fonts panel, set the Views font to Monaco 12
- Go to (it's the 
testcase under bug 3371)
==> You can see that the 'icon' and 'list' fonts are in Monaco 12, the Standard 
font is whatever you currently have in the Mozilla prefs as Serif font, and all 
the other fonts ('caption', 'menu' etc...) are in Geneva 10 which is the Small 
System font as listed (but non-modifiable) under the Appearance Control Panel.

Comment 11

18 years ago
QA Assigning non-confidential New/Assigned User Interface: Design Feedback bugs 
to Matthew Thomas (

Matthew Thomas is now the QA owner for the User Interface: Design Feedback 
component. (Bugs that involve UI issues in the Netscape-branded Mozilla browser 
should continue be QA assigned to
QA Contact: elig → mpt

Comment 12

18 years ago
Ben, if (a) Pierre's instructions work for you, and (b) you can fix bug 16729 
before beta 2, then please mark this bug as wontfix.

Removing dependency on bug 16729: this bug isn't dependent on 16729, it would be 
made obsolete by 16729.
No longer depends on: 16729


18 years ago
Target Milestone: --- → Future

Comment 13

18 years ago
If this is timetabled for `Future', it's irrelevant. This was intended as a 
temporary measure only.

*** This bug has been marked as a duplicate of 16729 ***
Last Resolved: 18 years ago
Keywords: verifyme
Resolution: --- → DUPLICATE

Comment 14

18 years ago
I confirm that I opened this bug as a temporary measure.
Verified dup.


16 years ago
Component: User Interface Design → Browser-General
Product: Browser → Seamonkey


10 years ago
Keywords: verifyme
You need to log in before you can comment on or make changes to this bug.