NotHereToPlayGames

It's been years since I've used it but I do seem to recall that I had to create the folder, that it did not exist by default. I cannot say if this will work though, it was pre-v49 that I've used it. I quickly turned into a Stylem/Stylus "junkie" and can't live without it.

In past versions of Chromium, I used this folder ~/.config/chromium/Default/User StyleSheets/Custom.css the same as {Profile}\Chrome\userContent.css file in Firefox. But I have not personally tried that in 360Chrome.

Which extensions are you using? Perhaps we can find a fix using only those extensions. edit - and which 360Chrome version is your preference?

@UCyborg Agreed. It certainly affects v11 more than other versions. Another test site presented very early in the thread is https://off-guardian.org/2021/09/22/30-facts-you-need-to-know-your-covid-cribsheet/ However, most of us (including me) that use v11 as our default-for-everything-browser have extremely valid reasons for using v11 over v13. Font issues that are easily fixable on three web sites out of the three thousand web sites that I have visited so far this year alone isn't going to be even a thumbtack let alone a nail in v11's coffin

Best route is via Stylus and a style sheet with something like "body {font-family: unset !important;" and that basically is the equivalent of unchecking the box in the Inspector.

I'm quite sure that they don't. Factory computers.

Updated download for v11 in first post.

This computer has an Nvidia GeForce GT 635. But I've witnessed that font-blur crap on hundreds of computers. The factory floor has 350+ computers, they all do that font-blur crap!

And those "colors" are there on your end whether you post your screencaps as jpg (where we can see all the colors) or as png (which hides those colors from us [alpha-blending?]). It's actually totally amazed me over the years on how RARE my eyesight is. There were people that tried to sue Microsoft when they pushed "cleartype". But only a very small percentage of the population can "see" the PROBLEMS with "cleartype".

Disable "libre franklin" font family and that web site displays correctly.

The Digital Spy problems all revolve around their use of a font called "libre franklin". My default settings block it via NoScript. The font is coming from gstatic.com and I disable gstatic fonts by default. Blocking that font also corrects the italics for Doctor Who. With that font allowed - With that font blocked -

Firefox does it also! My eyesight sees that crap without zooming in. It's "anti-aliasing" and it's ENABLED by default on most systems.

Definitely looks better!

I have pretty decent luck with fonts on my XP. But I do have to jump through some hoops to disable any and ALL "cleartype" and "anti-aliasing" and "sub-pixel" B&LLSH!T. When Win7 first came out, I landed in an MRI machine because of the MIGRAINES due to Win7's "cleartype" fonts! I've disabled "Segoe UI" ever since. Win10's default fonts don't give me migraines but I still disable "Segoe UI" at all costs. If fonts on my system rendered like the below screencap posted by Dave-H, I would be outside throwing that computer around so much that I'd be in prison for ten years for the massive disturbance of the peace I would be making. This looks absolutely HORRENDOUS. I count at least SIX unique colors for what is supposed to be rendered as "black" !!!

You should be able to edit the Clean Font Families with an // @exclude for your youtube URL. I'm not seeing any icon font squares on my end. What section of an MSFN page are you seeing that? Maybe an // @exclude entry for MSFN will also work best for you. edit - disregard, you did say the font square were only with your previous extension and that the Tampermonkey script solved that issue.

ps - I also suggest disabling DirectWrite font rendering. Unless your eyesight just can't see it, the screencap you posted has like EIGHT DIFFERENT COLORS where it's supposed to only be ONE COLOR. Dang near almost gives me a migraine just looking at your screencap.

Font issues seem to occur farily often in Chromium-based browsers. ESPECIALLY if the web master is a Firefox fan and they've learned that "rem-sized" fonts are often problematic in Chromium-based. Not saying it happens "all the time", probably only about 5% of the time. Seldom enough that all I've ever done when font issues arise is right-click and select Inspect and 99 times out of 100 you will find that the .css style for the problematic font is either "font-size rem" or "letter-spacing rem", just replace the "rem" with an equivalent "px" and problem solved. The "rem" font size/spacing nuance has been around since 2013 at least (based on a few Google searches). More often than not, it's because proper .css coding was not followed (but Firefox resorts to a fallback scaling so all the web master usually cares about is that it works in his beloved Firefox). It's actually quite common. I've known people to intentionally apply "rem" scaling in forum replies so that only Firefox users can read their reply (the Chromium crowd was smart enough to make the necessary corrections but the Firefox crowd was "self-amused" nonetheless). To make a long story short (too late?), you can just use the Inspect feature and change the font-size or letter-spacing. Or you can use Tampermonkey (this is the route I now use). There are three I recommend (I only use one, but you may want to try all three to see which you prefer). Browse over to GreasyFork.org and search for "global font". One is called "Global Font: Adobe-branded" and one is called "Global Font: Microsoft-branded". Both of those work really well. The third is the one that I use. Browse over to GreasyFork.ort and search for "clean font families". There's also some good scripts at GreasyFork.org if you want to always change a specific font family to your preferred font family. I'd have to dig through my archives but I think the one that I used to use as far as replacing specific font families with other font families came from there, unsure. The "clean font families" has been my go-to. I've not had any font rendering issues since I've started using that one a year or so ago.

As far as landfills and waste in general, I once heard that today's teenager consumes (ie, buys, wears, then throws away) more clothing in ONE YEAR than what we older generations did in FOUR YEARS. So the next time one of these "yutes" points a bony finger about "saving the planet", ask them what they think about the vast amounts of "textiles" that they throw away NOT because they outgrew them, but because they don't want to be seen wearing the same thing more than three times.

Don't forget the mushrooms, lardons, and pearl onions.

Eureka! Found it! v11 on the left, v12 on the right. The "separator" methodology was changed starting with v12 and v11 used the incorrect unicode character (at least without the aid of "extra" fonts). I use a different build base revision so my file numbers may differ from Humming Owl's file numbers. My XP builds do not have "extra" fonts installed and all font-fetches are blocked, so "mileage may vary".

For reference -- https://github.com/ChromeDevTools/devtools-frontend Still digging.

@Humming Owl -- Do you know by chance "where" these are as far as correcting them in v11? In v12 and higher, these are displayed as "pipes" aka "vertical bars" (the vertical line above the "Enter" key on most keyboards). https://en.wikipedia.org/wiki/Vertical_bar

That makes perfect sense. I used to use ProxHTTPSProxy. It basically ignores the "certificate" for the actual web site and only lets your browser see the "certificate" for ProxHTTPSProxy.

SSL "certification" is a complete and utter waste of time. It's a flawed technology, plain and simple. Even MALWARE sites know how to show a "green padlock". Gone are the days where "ssl" was for BANKING SITES ONLY - you know, back when that "green padlock" actually MEANT SOMETHING. Now it's "https everywhere" and that's the STUPIDEST thing the World Wide Web ever conceived!

Do you have this setting checked? I personally do not use this setting and find any-and-all "ssl warnings" to be a complete waste of time on XP.