Chrome font is wrong on OSX in classic skin

RESOLVED INVALID

Status

SeaMonkey
Themes
--
critical
RESOLVED INVALID
16 years ago
10 years ago

People

(Reporter: Mike Pinkerton (not reading bugmail), Assigned: andreww)

Tracking

({embed, topembed-})

Trunk
mozilla1.0.1
PowerPC
Mac OS X
embed, topembed-

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: helpwanted [adt3])

(Reporter)

Description

16 years ago
The font for buttons and menulists is totally wrong on OSX in classic. I'm not
sure what it needs to be, but it's not what we're using now.
(Reporter)

Comment 1

16 years ago
This is a requirement for embedding clients as well, it needs to be addressed by
beta.
Keywords: mozilla1.0, nsbeta1, topembed
(Assignee)

Comment 2

16 years ago
Ok, I need help from someone who has this knowledge to determine 
a) what does this font need to be
b) does this font need to be specific for OSX?
c) would this be something that needs -moz-appearance somehow?
d) wouldnt this simply be the system font that the user has preset or 
would we hard-code this font?
Whiteboard: helpwanted
> a) what does this font need to be

Lucida Grande (by default) drawn using Quartz anti-aliasing. (Drawing it through
the legacy QuickDraw API doesn't look right at all.)

> b) does this font need to be specific for OSX?

Yes.

> d) wouldnt this simply be the system font that the user has preset or 
> would we hard-code this font?

Doing this with the CSS system fonts would make sense if Mozilla used ATSUI
through Quartz for all font rendering on OS X.
(Assignee)

Updated

16 years ago
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.0.1

Comment 4

16 years ago
Would this also be the appropriate place to mention that when an aqua button is
clicked, the text shouldn't turn white? That's definitely not consistent with
the OS behavior.

Comment 5

16 years ago
See bug 102224 for some info on how broken system fonts are on Mac (thanks to
pierre's hack).
(Assignee)

Updated

16 years ago
Blocks: 110865
(Reporter)

Updated

16 years ago
Keywords: nsbeta1, topembed → nsbeta1+, topembed+
(Reporter)

Comment 6

16 years ago
i tried playing with several variations of fonts. Right now, mac classic on osx
gets Lucida Grande for the button font, and it looks like crap when drawn from
QuickDraw. Given that there's no way that we can actually call DrawThemeText
from layout, i think we're just plain boned here.

I think we're just stuck with cruddy looking widgets, and it's got nothing to do
with pierre's hack (if i am correctly understanding his hack, at least. the code
for rendering UI buttons doesn't go through that particular smarmitude).

anyone have any good ideas (and "turn on quartz rendering" isn't an idea)?

Comment 7

16 years ago
If Lucida Grande unQuartzed looks better than what Mac Classic uses for
non-button controls on OS X right now, and `We need Quartz' is a separate bug,
then this bug is a duplicated of bug 81178.
(Assignee)

Comment 8

16 years ago
Seems like we might take a "divide and conquer" approach here and start 
going over the different areas that contain text and begin to work out what 
font is correct and try to get that implemented.  Perhaps there  is a way to 
hit the 75-80% cases with some small number of changes.

Updated

16 years ago
Keywords: topembed+ → embed, topembed-

Updated

16 years ago
Whiteboard: helpwanted → helpwanted [adt3]

Comment 9

16 years ago
Can someone pls attach a screen shot of what this looks like?
(Reporter)

Comment 10

16 years ago
with the patch for quartz rendering, the osx classic skin looks great. i guess
that's good enough and we don't have to worry about this anymore.
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → INVALID

Comment 11

16 years ago
So what font is being used here? It should, of course, be Lucida Grande. If not,
then this bug should be reopened.
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.