Menu
I noticed today that a site I developed has suddenly stopped rendering the "Arial Black" font face in chrome.
Does anyone know if any recent Chrome updates could have caused "arial black" to stop working?
Even the example on w3schools has stopped working in chrome: http://www.w3schools.com/cssref/css_websafe_fonts.asp
811
Go to Control Panel > Appearance and Personalization > Display > Adjust ClearType text (on the left). Check the box entitled “Turn on ClearType.” After going through a short wizard, this will fix some of the text rendering issues in Chrome. Enable "Disable accelerated 2D Canvas" in Chrome.
The following fonts are found in the "OTHER" section of the font drop-down menu in the TEXT toolbar and are considered to be web-safe: Arial Black. Arial MT Condensed Light. Arial Narrow.
The operating system ships with Arial, Arial Black, Arial Narrow, and Arial Rounded MT. However, the default macOS font for sans-serif/Swiss generic font family is Helvetica. The bundling of Arial with Windows and macOS has contributed to it being one of the most widely distributed and used typefaces in the world.
It comes set by default with the latest Chrome update (Version 37.x) (Originally on Chrome 35 beta and not set by default) and it's how Chrome uses the DirectWrite API on Windows to render the font.
If you want the old behavior open chrome://flags/ and enable Disable DirectWrite.
This will disable the use of experimental DirectWrite font rendering system.
Also as noted in this bug report:
This all comes from DW treating font weights as different variations of the same font, unlike GDI. Thus Arial Black is considered to be Arial with a weight of 900 and that matches the specified family.
So if "Arial Black" falls back to "Arial" with a weight of 900 and weight of 900 in Arial is not the same 'weight' as Arial Black, then you will see the difference in the rendered font.
62
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
