Chrome does not render many default installed fonts on Windows
Reported by
f.con...@gmail.com,
May 1 2018
|
|
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0 Steps to reproduce the problem: 1. For your convenience: use a code editor with a split mode (code and preview at the same time), such as WeBuilder (www.webuilderapp.com, free test version). That will save you a lot of time. 2. Load the attached file and click the Horizontal Split tab. Make sure to selected Chrome as Preview sub mode, not IE. 3. Go to C:\Windows\fonts to see the names of the installed system fonts. 4. One by one, enter the font names in the CSS declaration, replacing 'Verdana'. And see that Chrome renders only a small number of them. Sometimes, such as the case with Copperplate Gothic, it only renders the Light variant, not the Bold. And declaring `font-weight:bold` then does not give the same result. Regarding the latter: I made a test version, using Copperplate Gothic Bold *Web*, that will show that. It is available on http://conijnconsultancy.com/storage/chrome-font-demo.html. What is the expected behavior? That Chrome renders all default installed fonts and font variants on Windows. What went wrong? Chrome doesn't render many of them. Did this work before? No Does this work in other browsers? Yes Chrome version: <Copy from: 'about:version'> Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 29.0 r0
,
May 2 2018
Thanks for clearing that up. Still, you would save I don't know how many webdesigners worldwide a couple of hours of detective work, and I don't know know how many web font downloads (waste of energy!), if you would make Chrome also match the font family names as they are listed by...... Chrome itself. Yes, Chrome, too, lists 'Copperplate Gothic Bold' and 'Copperplate Gothic Light' in the dropdown menu under Settings > Appearance > Customize fonts > Standard font. Then to not have Chrome web-render the first font if a webdesigners declares it as such in the CSS, that's nothing less than misleading i.m.o. I know the Chrome dev team did not do that intentionally, but I do find it very disappointing that you won't fix it. IE, Edge and Firefox all are webdesigner-friendly with this issue. And it ain't exactly rocket science. So I'm very sad that you are taking such a formal position. I hope you will have a change of heart.
,
May 6 2018
#2 - you can star issue 641861.
,
May 6 2018
@#3 -- I would have to read through that whole thread and I don't have the time for that. From scanning it, I cannot tell whether it comes down to the same cause. |
|
►
Sign in to add a comment |
|
Comment 1 by e...@chromium.org
, May 1 2018