Issue metadata
Sign in to add a comment
|
font-face mixed http https stops fonts rendering
Reported by
lewis.co...@gmail.com,
May 11 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36 Example URL: https://e-activist.com/page/23394/action/1 Steps to reproduce the problem: 1. visit a URL defining font-face with mixed content warnings from content of font-face & fallback font specified 2. Look at the whole lot of unrendered text What is the expected behavior? The fallback font to take over as the font-face is not correctly loaded What went wrong? No font is rendered unless I inspect element and remove the font-face Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? No Does this work in other browsers? No Firefox, Stable & Nightly Chrome version: 66.0.3359.139 Channel: stable OS Version: Xenial 64-bit Flash Version: N/A or default May require some form of flags for user-defined fonts. In the case of where I first encountered the problem, it should be fixed by the site owners, however as an end-user this is not very useful to me. It's made more complex by the fact that the place including the link to definition of webfont could be inline, imported in a stylesheet, or linked (as in this case) to an external CSS that then pulls in font-files.
,
May 16 2018
I see console message saying: Slow network is detected. See https://www.chromestatus.com/feature/5636954674692096 for more details. Fallback font will be used while loading: https://fonts.gstatic.com/s/rubik/v7/iJWBBXyIfDnIV7nEldWYwWL-6aJ8x8s.woff2 but all text are visible. Maybe my network isn't fast atm, I'll try later,
,
May 17 2018
On a fast network, I don't see the message in #2. #0, can you please explain a bit more when you wrote: > What went wrong? > No font is rendered unless I inspect element and remove the font-face I can't find where the text is not rendered.
,
May 17 2018
,
May 17 2018
If you look at the attachments, you'll see pictures of what I could see. I've written to the people running the petition so they may have fixed their CSS to no longer call mixed URL's but it doesn't solve the problem for other sites. I've just taken the screenshot attached today. Problem is still there, not part of just blocking http content on https. Even when I select the shield in the address bar (resulting in the red error message near padlock url bar display) the fonts don't render. What happened was that I visited a page and it looked like a layout block diagram, no body.
,
May 17 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 17 2018
Thank you for the feedback! I can't reproduce that on my: Linux stable 66.0.3359.181 Win stable 66.0.3359.170 Win Canary 68.0.3427.0 Is this happening on single machine, or on multiple machines for you?
,
May 17 2018
I'm getting the same thing on other machines, I've tried incognito mode, even a windows PC. page loads with fonts missing.
,
May 17 2018
Xenial Version 66.0.3359.181 (Official Build) (64-bit) Win10 Version 66.0.3359.139 (Official Build) (64-bit) Also happens to firefox
,
May 17 2018
Unable to reproduce the issue on chrome reported version 66.0.3359.139 latest stable# 66.0.3359.181 using Ubuntu 17.10 with steps mentioned below: 1) Launched chrome reported version and navigated to URL: https://e-activist.com/page/23394/action/1 2) Scrolled the page, able to see font rendering as excepted. Observations: Also tested the issue on latest Beta# 67.0.3396.48 and latest chrome# 68.0.3432.0 and observed same behaviour as mentioned above. @Reporter: Please find the attached screencast for your reference and try to test this issue on latest chrome stable# 66.0.3359.181 and let us know if the issue still persists. You can download latest chrome stable from URL: https://www.chromium.org/getting-involved/dev-channel. Thanks!
,
May 23 2018
,
May 24 2018
As per comment#10, we are unable to reproduce the issue on chrome reported version 66.0.3359.139 and waiting for Feedback from the reporter to confirm it on latest stable, hence adding Needs-Feedback label to it. Thanks!
,
May 30 2018
The NextAction date has arrived: 2018-05-30
,
Jun 13 2018
Closing as no further feedback. If you or anyone can reproduce, please leave comments or file a new issue. Thank you for reporting this to us anyway.
,
Jun 13 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, May 14 2018