In Mac OS 10.10 (Yosemite), the system font is .Helvetica Neue DeskInterface. But this is not included in font.system.whitelist in TB 5.5a4. Unless doing so will cause fingerprinting concerns, we should add it. I will attach a screenshot that shows that buttons do not look good without it.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items
0
Link issues together to show that they're related.
Learn more.
I wonder what is making the button look odd. Has the previous UI font (Lucida Grande) been removed from 10.10? Maybe a different random font is being used because it is missing?
We could decide to accept that Yosemite is distinguishable, and whitelist that font. Is it a widespread problem in the UI?
I wonder what is making the button look odd. Has the previous UI font (Lucida Grande) been removed from 10.10? Maybe a different random font is being used because it is missing?
Lucida Grande is still present. I don't know what font is being used on Yosemite. Is there a way I can find out? Computed CSS does not seem to provide the answer (it just lists "Helvetica Neue DeskInterface").
We could decide to accept that Yosemite is distinguishable, and whitelist that font. Is it a widespread problem in the UI?
It is a fairly widespread problem, although some buttons look OK; maybe those portions of the UI use a fixed height in CSS or XUL.
Is there any chance that text is being rendered using font A but metrics (e.g., height) are being derived from font B? The behavior Yawning saw in #17550 (moved) makes me suspicious - even if the wrong font is used, I would not expect the height to be such a mismatch for the rendered text.
I wonder what is making the button look odd. Has the previous UI font (Lucida Grande) been removed from 10.10? Maybe a different random font is being used because it is missing?
Lucida Grande is still present. I don't know what font is being used on Yosemite. Is there a way I can find out? Computed CSS does not seem to provide the answer (it just lists "Helvetica Neue DeskInterface").
For Firefox 38.0, I often use the two Firefox addons, DOM Inspector and Element Inspector. Then you can shift+right-click on the button and it opens a window showing information about the button. Then under the menubar, choose View > Object Viewer > Used Font Faces.
We could decide to accept that Yosemite is distinguishable, and whitelist that font. Is it a widespread problem in the UI?
It is a fairly widespread problem, although some buttons look OK; maybe those portions of the UI use a fixed height in CSS or XUL.
Is there any chance that text is being rendered using font A but metrics (e.g., height) are being derived from font B? The behavior Yawning saw in #17550 (moved) makes me suspicious - even if the wrong font is used, I would not expect the height to be such a mismatch for the rendered text.
That's a very good point. Yawning's bug is especially weird, because the element sizes go so badly wrong.
For Firefox 38.0, I often use the two Firefox addons, DOM Inspector and Element Inspector. Then you can shift+right-click on the button and it opens a window showing information about the button. Then under the menubar, choose View > Object Viewer > Used Font Faces.
Thanks. Testing with the Page Info dialog (which has a "Save As..." button on the "Media" tab), Kathy and I had to "walk up the tree" a little before anything was displayed in the "Object - Used Font Faces" area. When we get to the grandparent element (an hbox), the Used Font Faces area shows "Helvetica". I am not sure why that font is selected, but I guess some code is substituting plain "Helvetica" for ".Helvetica Neue DeskInterface". I do not know if that is expected or not.
It seems like Helvetica just looks bad in some situations. When we add style="font-face: Helvetica" via DOM Inspector in Firefox 43 beta and see the same rendering problem. If we add style="font-face: Lucida Grande" it looks fine. How difficult is it to control which font is substituted when a font is not available?