"sans serif" selected in Google Docs doesn't use a sans serif font
Categories
(Core :: Layout: Text and Fonts, defect)
Tracking
()
People
(Reporter: selenamarie, Unassigned)
Details
Attachments
(6 files)
not-sans-serif.png
A friend pointed out the glitch - displaying a serif font in Google Docs when a sans serif one is requested -- in the image attached. It was apparently a recent regression and the user is on 69.0b5.
|
||
Updated•6 years ago
|
|
|
||
Comment 1•6 years ago
|
||
Could you (or your friend) provide STR? In particular: how do you get Google Docs to offer you the generic "Sans Serif" as a font option?
For me, that dropdown menu defaults to "Arial". And when I open the dropdown, I don't see "Sans Serif" anywhere the dropdown menu, nor is it available if I click "more fonts" and use the searchbox to search for "Sans Serif". (That gives me no results.)
|
|
||
Comment 2•6 years ago
|
||
|
|
||
Comment 3•6 years ago
|
||
I'm wondering if your friend has a local font that is literally named "Sans Serif" (i.e. in the list of fonts on the right side of the dialog in my attached screenshot), and if so, I'm wondering if that font might be:
(1) not in fact sans serif :)
...or:
(2) having trouble being rendered in Firefox for some reason.
It would be useful to know whether that is where this Sans Serif font is indeed coming from (or where they're getting it, if not from that list), and also whether they see different behavior in Chrome.
|
Reporter | |
Comment 4•6 years ago
|
||
|
|
Reporter | |
Comment 5•6 years ago
|
||
|
|
Reporter | |
Comment 6•6 years ago
|
||
To add to the mystery, when they use Chrome, the same menu item shows "Arial". See new attachments
|
|
Reporter | |
Comment 7•6 years ago
|
||
Arial had been disabled in FontBook. Interesting. Does Chrome maybe bundle Arial?
|
|
||
Comment 8•6 years ago
|
||
And un-disabling it fixes the bug, I imagine?
It's... still really odd that GDocs shows a non-sans-serif font named "Sans serif" in place of Arial when that happens.
|
|
||
Comment 9•6 years ago
|
||
(In reply to Daniel Holbert [:dholbert] from comment #8)
It's... still really odd that GDocs shows a non-sans-serif font named "Sans serif" in place of Arial when that happens.
This isn't what happens for me, actually (in MacOS High Sierra, with Firefox 69.0b5). The same font names still show up in GDocs, but they're just rendered using the default font.
|
|
||
Comment 10•6 years ago
|
||
|
|
||
Comment 11•6 years ago
|
||
...and here's a screenshot of Chrome under the same scenario.
Notice that "Arial" and "Courier New" are rendered using their respective fonts (or at least something that looks like them), despite the fact that I disabled these font families in FontBook -- but "Impact" is rendered using a fallback font, as in Firefox.
|
|
Reporter | |
Comment 12•6 years ago
|
||
(In reply to Daniel Holbert [:dholbert] from comment #8)
And un-disabling it fixes the bug, I imagine?
Yes, it fixed it.
It's... still really odd that GDocs shows a non-sans-serif font named "Sans serif" in place of Arial when that happens.
Yes.
(In reply to Daniel Holbert [:dholbert] from comment #11)
...and here's a screenshot of Chrome under the same scenario.
but "Impact" is rendered using a fallback font, as in Firefox.
It smells like an aggressive cache for local fonts.
|
||
Comment 13•6 years ago
|
||
I wonder if the document in question was created on a machine that had a font actually named Sans Serif (maybe some Linux setup?), and so that name was stored in the document and shown in the UI regardless of whether it was available or not. Otherwise, I don't know how to get that to show up in the Font menu on a typical Mac where no such font family exists.
Description
•