Squarespace based podcast blog – font rendering issue

For support with specific websites

Moderator: trava90

Forum rules
Please always mention the name/domain of the website in question in your topic title.
Please one website per topic thread (to help keep things organized). While behavior on different sites might at first glance seem similar, they are not necessarily caused by the same.

Please try to include any relevant output from the Toolkit Error Console or the Developer Tools Web Console using the following procedure:
  1. Clear any current output
  2. Navigate or refresh the page in question
  3. Copy and paste Errors or seemingly relevant Warnings into a single [ code ] block.
KlarkKentThe3rd
Astronaut
Astronaut
Posts: 617
Joined: 2018-04-20, 20:31

Squarespace based podcast blog – font rendering issue

Post by KlarkKentThe3rd » 2021-06-27, 08:55

Might as well. For the last few releases of PM I had this specific podcast website display text in a pale and thin manner. Attached are screenshots of pale/thin (PM) and contrasty/thick (Waterfox). Website link: http://www.supermarcatobros.com/podcast ... tle-themes

Based on what scripts have to run, the website is built with Squarespace. I am using PM 29.2.1

Browser Console gives me this:

Code: Select all

yui: NOT loaded: squarespace-polyfiller_modern  
common-vendors-stable-692c8190cb7f9d38c3f12-min.en-US.js:1:36594
yui: NOT loaded: squarespace-polyfiller_legacy  
common-vendors-stable-692c8190cb7f9d38c3f12-min.en-US.js:1:36594
yui: NOT loaded: squarespace-moment_js_vendor  
common-vendors-stable-692c8190cb7f9d38c3f12-min.en-US.js:1:36594
yui: NOT loaded: squarespace-cldr_resource_pack  
common-vendors-stable-692c8190cb7f9d38c3f12-min.en-US.js:1:36594
yui: NOT loaded: squarespace-common_vendors_stable  
common-vendors-stable-692c8190cb7f9d38c3f12-min.en-US.js:1:36594
yui: NOT loaded: squarespace-common_vendors  
common-vendors-stable-692c8190cb7f9d38c3f12-min.en-US.js:1:36594
yui: NOT loaded: squarespace-performance  
common-vendors-stable-692c8190cb7f9d38c3f12-min.en-US.js:1:36594
You do not have the required permissions to view the files attached to this post.

User avatar
Moonchild
Project founder
Project founder
Posts: 39725
Joined: 2011-08-28, 17:27
Location: Sweden

Re: Squarespace based podcast blog – font rendering issue

Post by Moonchild » 2021-06-27, 12:16

Here's what it looks like for me:
FireShot Pro Screen Capture #276 - 'Episode 471_ Battle Themes — Super Marcato Bros_' - www_supermarcatobros_com_podcast_2021_6_6_episode-471-battle-themes.jpg
Which is fine and perfectly readable (and actually looks better than FireChrome's rendering IMO).
If you tweaked contrast parameters in Pale Moon or are overriding font weights, then this might be the result. The font used (Raleway) is rather anaemic.
You do not have the required permissions to view the files attached to this post.
"Sales hates anything that can't be turned into a confident sentence." - anonymous warehouse worker
"Why debate someone you fundamentally don't trust?" - Dario Amodei
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

KlarkKentThe3rd
Astronaut
Astronaut
Posts: 617
Joined: 2018-04-20, 20:31

Re: Squarespace based podcast blog – font rendering issue

Post by KlarkKentThe3rd » 2021-06-27, 13:12

No, cannot remember doing any overriding.
You do not have the required permissions to view the files attached to this post.

User avatar
BenFenner
Keeps coming back
Keeps coming back
Posts: 987
Joined: 2015-06-01, 12:52
Location: US Southeast

Re: Squarespace based podcast blog – font rendering issue

Post by BenFenner » 2021-06-27, 15:49

I'm also seeing the high-contrast rendering (as high contrast as one can get with a medium-shaded background like the one used) on Windows 7.
Font faces can be quite different on Linux, so I can go check that and report back.

Edit: Different font on Linux, but still black text (or nearly so). Something is likely up with your particular setup... :|

User avatar
Moonchild
Project founder
Project founder
Posts: 39725
Joined: 2011-08-28, 17:27
Location: Sweden

Re: Squarespace based podcast blog – font rendering issue

Post by Moonchild » 2021-06-27, 16:18

This is the point where the output of help -> troubleshooting information might be helpful.
"Sales hates anything that can't be turned into a confident sentence." - anonymous warehouse worker
"Why debate someone you fundamentally don't trust?" - Dario Amodei
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

coffeebreak
Moon Magic practitioner
Moon Magic practitioner
Posts: 2985
Joined: 2015-09-26, 04:51
Location: U.S.

Re: Squarespace based podcast blog – font rendering issue

Post by coffeebreak » 2021-06-27, 20:05

KlarkKentThe3rd wrote:
2021-06-27, 08:55
text in a pale and thin manner
I don't see this either (using PM 29.2.1, Win 7 x86).

For me the text looks like that in Moonchild's screenshot.
supermarcatobros-fonts.png
Btw, I do see the same console messages as you posted, but given how fonts display here, they are presumably not relevant.
You do not have the required permissions to view the files attached to this post.

User avatar
RealityRipple
Keeps coming back
Keeps coming back
Posts: 958
Joined: 2018-05-17, 02:34
Location: Los Berros Canyon, California

Re: Squarespace based podcast blog – font rendering issue

Post by RealityRipple » 2021-06-27, 20:27

It's using a Google-hosted font called Raleway. If "Allow pages to choose their own fonts" is unchecked (under Advanced in the screenshot you posted), or if you have an adblocker or cross-origin css blocker of some sort enabled, the font's not gonna load. You should also check the Network tab of the developer tools console to make sure all the requests to "fonts.googleapis.com" and "fonts.gstatic.com" succeeded.

User avatar
Moonchild
Project founder
Project founder
Posts: 39725
Joined: 2011-08-28, 17:27
Location: Sweden

Re: Squarespace based podcast blog – font rendering issue

Post by Moonchild » 2021-06-27, 20:44

RealityRipple wrote:
2021-06-27, 20:27
If "Allow pages to choose their own fonts" is unchecked (under Advanced in the screenshot you posted), or if you have an adblocker or cross-origin cs....
irrelevant because you can clearly see in the screenshot that the correct webfont is in use.
"Sales hates anything that can't be turned into a confident sentence." - anonymous warehouse worker
"Why debate someone you fundamentally don't trust?" - Dario Amodei
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

KlarkKentThe3rd
Astronaut
Astronaut
Posts: 617
Joined: 2018-04-20, 20:31

Re: Squarespace based podcast blog – font rendering issue

Post by KlarkKentThe3rd » 2021-06-27, 23:26

Perhaps this is entirely the fault of my particular "build". And if that is the case, there is nothing Moonchild can do about it.

User avatar
RealityRipple
Keeps coming back
Keeps coming back
Posts: 958
Joined: 2018-05-17, 02:34
Location: Los Berros Canyon, California

Re: Squarespace based podcast blog – font rendering issue

Post by RealityRipple » 2021-06-28, 07:01

Moonchild wrote:
2021-06-27, 20:44
RealityRipple wrote:
2021-06-27, 20:27
If "Allow pages to choose their own fonts" is unchecked (under Advanced in the screenshot you posted), or if you have an adblocker or cross-origin cs....
irrelevant because you can clearly see in the screenshot that the correct webfont is in use.
Google separates fonts by their weight and whether or not they're italic. If the weight the page uses fails to load, it might fall back to another one. The site in question loads weights from 100 to 700, but seems to primarily use 500. The picture looks like it fell back to 100.

KlarkKentThe3rd
Astronaut
Astronaut
Posts: 617
Joined: 2018-04-20, 20:31

Re: Squarespace based podcast blog – font rendering issue

Post by KlarkKentThe3rd » 2021-06-28, 13:23

RealityRipple wrote:
2021-06-28, 07:01
If the weight the page uses fails to load, it might fall back to another one. The site in question loads weights from 100 to 700, but seems to primarily use 500. The picture looks like it fell back to 100.
You might be on to something.

User avatar
Moonchild
Project founder
Project founder
Posts: 39725
Joined: 2011-08-28, 17:27
Location: Sweden

Re: Squarespace based podcast blog – font rendering issue

Post by Moonchild » 2021-06-28, 13:44

Doesn't make much sense to me. Why would something be blocking 1 font variant but not another from the same service?
"Sales hates anything that can't be turned into a confident sentence." - anonymous warehouse worker
"Why debate someone you fundamentally don't trust?" - Dario Amodei
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

User avatar
BenFenner
Keeps coming back
Keeps coming back
Posts: 987
Joined: 2015-06-01, 12:52
Location: US Southeast

Re: Squarespace based podcast blog – font rendering issue

Post by BenFenner » 2021-06-28, 13:52

As an experiment, I used the dev tools to change the font weight from 500 to 100 and it reproduced the OP's problem.

Edit: Well nearly so. It looks nearly identical, except the word "Battle!" on my page is still bold/strong... That isn't the case in the OP's first screenshot...

User avatar
RealityRipple
Keeps coming back
Keeps coming back
Posts: 958
Joined: 2018-05-17, 02:34
Location: Los Berros Canyon, California

Re: Squarespace based podcast blog – font rendering issue

Post by RealityRipple » 2021-06-28, 14:53

The word "Battle" next to Xenoblade Chronicle's 2's battle theme is separately bolded without using a number, meaning it's using 700 instead of 500.

The reasoning why one might be loaded while another (or others) aren't could be either because the CSS (or the URL) got mangled, or because one or more of the fonts' filenames have characters that are being blocked. I often run into issues on websites where an image will have a hexadecimal name and will get blocked just because the first two characters of the name are "AD". In Google fonts' case, it's base64, but it's still possible that something in "1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrE" was acceptable while "1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrE" was blocked. Or it could literally have been randomly caused by timeout or a prematurely closed connection and then cached that way. But a mangled URL would be the most straightforward way I see, mostly because each weight is separated by semicolon: if something stripped everything after that semicolon from the URL, it'd only load 100 weight.