Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug: Browser Extension] Some of my site's fonts are blocked by extension until I refresh page #3054

Open
ghost opened this issue Oct 1, 2019 · 2 comments

Comments

@ghost
Copy link

ghost commented Oct 1, 2019

Since using Webhint, I've discovered a weird bug that I thought was a Chromium issue, but I've been able to demonstrate that it's the Webhint extension that's causing the problem.

If the Webhint extension is active, then when I first load my page, there's a delay between the time that the default/fall-back sans-serif fonts are displayed and when the specified, "first-choice" webfonts are used, in this case, Cabin. No real problem there, although it would be nice if there wasn't a delay.

Here's the real problem, though:

After the Cabin fonts are fully loaded on the site, only the bold, italic, and other non-regular fonts are employed. The site continues to use the fallback, generic sans-serif fonts.

If I then refresh the page, however, the regular fonts convert to the specified "Cabin" font.

The site in question is https://thomasbrodhead.com

I'm on Windows 8.1, using the current Chrome (77)

Here are screen shots that illustrate the problem:

https://bmt-systems.com/tmb-01-annotated.jpg

https://bmt-systems.com/tmb-02-annotated.jpg

https://bmt-systems.com/tmb-03-annotated.jpg

I've set the Webhint browser extension to be active in Incognito mode, btw.

@molant
Copy link
Member

molant commented Oct 1, 2019

Does this issue happen with just the extension installed or when you run an analysis with it?

@ghost
Copy link
Author

ghost commented Oct 1, 2019

This doesn't happen during analysis, because the browser refreshes during that process.

This also doesn't happen if Chrome is already open in any other form. A single instance of Chrome is what is needed to reproduce the behavior.

With all instances of Chrome closed, open Chrome directly in an incognito window by issuing this command at a CMD prompt:

"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" -incognito "https://thomasbrodhead.com"

On my Windows 8.1 machine, the described buggy behavior obtains. On the other hand, if a regular instance of Chrome is already open, opening the incognito window using the method described will not reproduce the buggy behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant