A particular web font is not displayed in Google Chrome. Google chrome fonts Font Amazing icons that don't show up in Chrome related to MaxCDN related to cross resource sources

Periodically, after updating the Chrome browser, users had problems with the font: it became soapy, fuzzy, blurry, etc. Up to version 51 inclusive, this problem was easily solved, but updating to version 52 brought a big surprise to all browser users...

How to explain such a step is absolutely unclear, but on forums, including the official Google forum, there are a huge number of angry reviews with requests and even demands to return everything back.

At the time of writing, August 6, we already have the next version of the Chrome browser (52.0.2743.116), but nothing has changed. Apparently the developers know better which font is more convenient for users and should not give them freedom of choice...

What problems may occur in the browser?

A problem with fonts can manifest itself in different ways. For some, the font is simply blurry and unclear. For some, the bold font has a shadow or is not at all different from the usual one:

Someone has problems with the display of the font on the VKontakte website: it is cloudy, completely unreadable, cuts and strains the eyes. Example:

For some, instead of black, all the letters are gray, barely visible on a white background:

And some users experience complete nonsense and horror: the fonts are broken and look crooked:

How to solve the problem with fonts in Google Chrome and return them to a readable state?

If Chrome version is 51 and lower, then you, and if 52 and higher, then listen carefully... Currently, there is no solution to how to make fonts clearer using Chrome itself - the developers have deprived users of influencing this by removing the DirectWrite parameter from the experimental settings!

There are only two ways to solve this problem:

• First, switch to another browser, such as Firefox. By the way, the latest versions of Opera have the same problem with fonts as Chrome, since they are based on the same engine.
• Secondly, roll back Chrome to the previous version, more precisely to the one where the problem was not yet present (51.0.2704.106), and configure the DirectWrite parameter. But there is one catch...

Google developers have outwitted everyone here too :) It is impossible to roll back through the settings of the browser itself - there is no such option. Even if you uninstall the current version of the program, you will not find installation files of previous versions on the official website.

How to roll back to a previous version of Google Chrome

All that remains is this diagram:

Anyone who wants can search on their own, but we have already found it, downloaded it, and now we are sharing with you a link on Yandex.Disk: Google Chrome 51.0.2704.106 (there is a version for both 64bit and 32bit systems).

1. Before deleting Chrome, synchronize all the necessary data with your Google account so that it does not disappear! To do this, in the address window of your browser, type chrome://settings/syncSetup and press enter. In the window that opens, check the boxes next to all the necessary items, or better yet, just select the “Synchronize everything” option, as in the screenshot below - it will be more reliable :)

Wait a while for synchronization to complete, especially if you previously had this option disabled.

1. After installing version 51.0.2704.106, return your previous Chrome settings by syncing and be sure to disable automatic updates to the latest version, otherwise the browser will be updated again and everything done will go down the drain!

How to disable Chrome updates

To prevent the browser from updating, we do one trick. Go to the folder c:\Program Files\Google\Update\ or c:\Program Files (x86)\Google\Update\, if you have a 64-bit version of the OS, delete the file GoogleUpdate.exe.

That's it, no problems :) On the Internet they recommend editing registry entries, changing Windows group policies, adding administrative templates, etc., etc. As always, most of these instructions were written by those who did not do any of this themselves, but simply copied from each other . None of this is needed. Simply delete the GoogleUpdate.exe file and Chrome will no longer be able to update.

When, after some time, you decide to install the latest version of Google Chrome (if this happens), simply manually download the installation file from the official website and run it. No problem!

P.S. (Update 06/2018)

Many users were helped by changing the font-cache-scaling parameter in the experimental settings. To do this, copy and paste into the address bar chrome://flags/#enable-font-cache-scaling, then select the “Disabled” state as shown in the screenshot:

Friends, did you manage to solve the problem of blurry fuzzy font in Google Chrome using these instructions? Share this article with your friends using the social buttons. networks - they will definitely thank you, because they probably experience the same problems with fonts as you.

Google Chrome font has changed (4)

Just noticed on several sites that the awesome icons aren't showing font in Google Chrome. The console displays the following error:

Thanks for any help/explanation!

This issue of accessing fonts - amazing assets has been a problem for many people without a comprehensive explanation and resolution to the problem.

What is CORS:

Copy Resource Sharing (CORS) is a mechanism that uses additional HTTP headers to allow a user agent to access selected resources from a server in a different origin (domain) than the site currently being used. A user agent makes a cross-origin HTTP request when it requests a resource from a different domain, protocol, or port than the one from which the current document originated.

Problem:

The problem is related to the way the font-amazing fonts are loaded.

@font-face( font-family:"FontAwesome"; src:url("../fonts/fontawesome-webfont.eot?v=4.2.0"); src:url("../fonts/fontawesome-webfont .eot?#iefix&v=4.2.0") format("embedded-opentype"),url("../fonts/fontawesome-webfont.woff?v=4.2.0") format("woff"),url( "../fonts/fontawesome-webfont.ttf?v=4.2.0") format("truetype"),url("../fonts/fontawesome-webfont.svg?v=4.2.0#fontawesomeregular") format ("svg"); font-weight:normal; font-style:normal)

Fonts are loaded via style sheet (CSS). The situation we have here:

Solution:

Although CORS rules have been created in your file storage, such as S3, and access to the resource has been granted to the given domain, when the CDN tries to download the fonts specified in the CSS, the source/domain specified when downloading those fonts is from the CDN, but the CORS access not provided to the CDN domain.

Create a CORS rule for your CDN domain.

I'm using a CDN which doesn't allow me to modify its answer, so I modified font-awesome.min.css by replacing the relative path with an absolute path and it worked.

The problem is not with the CSS file, but with the way it works with the font file. The font-awesome.min.css file has lines like

@font-face(font-family:"FontAwesome"; src:url("../fonts/fontawesome-webfont.eot?v=4.2.0"); src:url("../fonts/fontawesome-webfont .eot?#iefix&v=4.2.0") format("embedded-opentype"),url("../fonts/fontawesome-webfont.woff?v=4.2.0") format("woff"),url( "../fonts/fontawesome-webfont.ttf?v=4.2.0") format("truetype"),url("../fonts/fontawesome-webfont.svg?v=4.2.0#fontawesomeregular") format ("svg"); font-weight:normal; font-style:normal)

which force the browser to request the corresponding font file (eot, woff, ttf or svg) from the same server as the CSS file. This is logical and correct.

However, when the browser requests this font file from cdn.keywest.life, it reads the Access-Control-Allow-Origin header headers and doesn't find it, so it gives this error message. (This looks like a browser bug to me because it comes from the same server as the CSS file).

Instead, when you use maxcdn.bootstrapcdn.com the response includes an Access-Control-Allow-Origin:* header and the browser accepts that font file. If your cdn server included this header, it will work too.

If you have an Apache server, see this answer: Font-awesome not rendering properly in Firefox / how to sell via CDN?

Sometimes, after the latest update to the Chrome browser was released, many users have a problem with the display of the font, namely, it becomes fuzzy, blurry, making it impossible to read anything.

In older versions, before the release of version 51, solving this problem was not difficult, but with the advent of version 52, the developers presented users with a real surprise, unfortunately, an unpleasant one.

How to change unreadable fonts

The creators of Google Chrome decided to remove the ability to personalize the appearance of the font using the experimental option “Disable DirectWrite Windows,” which was a real lifeline for users suffering from fuzzy fonts. Now it has been removed.

How such a step can be explained is completely unclear, but on the forums, including the official Google forum, you can find a large number of negative reviews, in which they not only ask, but demand that everything be returned as it was. But it looks like the developers will leave everything as it is.

Problems using the browser

The problem with displaying fonts manifests itself in various ways.

First, you need to find out what version of Google Chrome you have installed, which requires typing chrome://help/ in the address bar and pressing enter. The “about the program” page will immediately open.

If your browser has version 52 or higher, then it would be a good idea for you to familiarize yourself with the methods below. Although there is currently no method by which you can use the capabilities of Google Chrome itself to make fonts clear, since thanks to the developers, users have lost the chance to influence this, there are still a few tricks

There are only 2 options to solve this problem:

1. Start working with another browser, for example, Firefox. The latest version of Opera, like Chrome, has a number of problems with the display of fonts, in particular with its color, which is explained by the same engine on which they were developed.
2. Roll back Google Chrome to a previous version when there were no such problems, and configure the DirectWrite parameter. However, there is one caveat: there is no way to roll back using the settings of the browser itself, since there is no such option. Even if you uninstall the current version of Google Chrome, you will not be able to find installation files for earlier versions on the official developer website.

Rollback to a previous version of Chrome

In order to do this, you need to follow this scheme:

Before deleting the browser, you need to synchronize all the necessary information with your Google Chrome account so as not to lose it. To do this, you need to type chrome://settings/syncSetup in the address window of your browser, and then press enter. After this, a window will open where you can mark the items you need, or better yet, just select the “Synchronize everything” option. Now you need to wait a little while until synchronization is completed, especially if until this moment this option was disabled.

After you install the previous, normally working version of Google Chrome, using synchronization again, you need to change all the browser settings to the previously used ones, be sure to turn off automatic updating to the new version first, otherwise Chrome will return everything as it was, and you will only waste your money your time.

Disable Chrome update

To prevent Google Chrome from updating itself, you should use one trick. Go to c:\Program Files\Google\Update\ or c:\Program Files (x86)\Google\Update\ if your computer is a 64-bit operating system, and delete one GoogleUpdate.exe file.

You can find a large number of recommendations on the Internet that insist on editing registry entries, changing Windows Group Policy, adding administrative templates, and the like. As a rule, most of these instructions were compiled by those users who did not do all this themselves, but only rewrote what they had previously seen on some forum. To solve such a problem, all these actions are not needed. It is enough to delete the GoogleUpdate.exe file and Google Chrome will no longer update itself.

If you ever need to install a new version of the Chrome browser, in this case the user himself will need to go to the official website of the developers and download the installation file, and then install it successfully. As you can see, there are no problems with disabling browser updates, everything is very simple and easy.

By following these tips, you can rid your browser of problems with font display, change its color to normal, and work with Google Chrome as before.

After a test installation of the Google Chrome Canary browser on a new Windows PC, broken fonts were discovered, both in the interface of the browser itself and on the sites that opened in it.

It's no secret that rendering is far from always ideal, but we did not expect such an occurrence on this particular machine, since we have never seen anything like this with Chrome Stable versions.

But I had to...

You can see what the mentioned problem looked like externally in the screenshot below. We made the upper part immediately after installation , and the lower one - after the bug is fixed. And please note, this is the settings menu page (the so-called chrome://flags page).

Of course, we also assumed that one of the reasons for this phenomenon could be that Canary is the newest version of the browser, and perhaps something is still being finalized and remade in it that is not yet even in the Stable version of Chrome.

However, further reflection led to the idea that this problem can also be successfully created by the computer’s own hardware and/or drivers installed on it. In addition, an incidental “Googling” of information on the topic showed that similar questions have periodically arisen among users since the time Chrome 3.

And the methods used to eliminate the bug were also very different, in particular disabling or DirectWrite, launching Chrome with different starting parameters, etc. Almost all of them are years old, of course, and are no longer relevant for the latest versions of the browser. But some of the “classics,” as it turned out, have not lost their former effectiveness. So,..

what to do if broken fonts appear in Google Chrome Canary:

• go to " Settings " (through chrome://settings/ or via " Menu«);
• Scroll to the bottom of the page and click “ Additional «;
• then scroll the page again to the section “ System«;
• and in it we disable the function “ Use hardware acceleration (if available) «;
• restart Chrome.

After that, broken fonts “corrected” themselves. But it is also worth noting that disabling the hardware acceleration function in this particular situation should be perceived as the lesser of two evils, since this can negatively affect the browser's performance in a number of cases (more precisely, when performing certain tasks). However, you can enable the function at any time by repeating the given algorithm of actions.