NotHereToPlayGames

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.

I'm still allowed to quote Vistapocalypse. D.Draker is not.

It seems to only happen to me when several tabs have a "flashing cursor" (ie, this reply box at MSFN). But for me it's "rare". I can have twenty tabs open all with a "flashing cursor" and be perfectly fine for several hours. Then other days I only have two tabs open and my fonts disappear randomly.

Just close and relaunch. No need for the CCleaner step in the middle. Still haven't been able to find a fix for it. Was very common if you read forum posts circa 2018 or thereabouts.

Makes sense to me. I'm still no fan of "invite-only" type of software. I do wish that Dixel would be as "public" as Humming Owl and I both are. Google Engineers have zero interest in reverse-engineering "loaders" that a tiny handful of users even know about. (ps, how's this for a chuckle, I actually used to think that you and Dixel were the same person, just logging in under different usernames, lol.)

ps - I say that speaking for me MYSELF. Others have to decide for themselves. Which has always been my philosophy regarding web browsers. There is no "best browser". We all must decide for ourselves what works for our own needs. I reiterate, I have nothing against Dixel's "loader". It is not for ME. But that does not mean it isn't for you.

I see no need to reinvent the wheel. If Dixel has something that works for you, then by all means use it. I myself do not trust a loader program that is as GIGANTIC as Dixel's loader program (16.5 MB for the version he shared with me) when Dixel chooses to HIDE the source code for that loader. Nothing against that, don't misread. It is a perfectly legit software methodology. (Closed source versus Open source.) It appears to be a spin-off of an old Opera Loader. If you view the loader in a Hex Editor, you will find Opera Portable Light text. You will also find opera_46_hackerman. Who is opera_46_hackerman? Why should we blindly trust opera_46_hackerman without knowing who he is? Humming Owl and I provide every detail required to build our builds, we aren't hiding anything, we let people critique our work publicly (not easy for me at times, I admit). I cannot speak towards the legality of "opera_46_hackerman" breaking license agreements. Nor for Dixel taking a "opera_46_hackerman" project and extending it toward 360Chrome. That's not to say that Humming Owl and I have not broken any license agreement with the original 360Chrome software company - but we aren't hiding either, the original developer can find us rather easily. Chromium is OPEN-SOURCE software. So is 360Chrome. There isn's a single solitary file that I cannot open and see what's inside, edit if needed, repackage, and then use. With Dixel's loader, I cannot see what's inside. Everybody has to choose their own level of paranoia and I may mock other's paranoia every once in a while, but I myself cannot trust a 16.5 MB loader program that I cannot see for myself what it does. To each their own. Mileage may vary.

Reminds me of a story from my college days. One of my best friends' parents had a lake cottage we would have lake parties at during the summer. We're all sitting around and one of the guys starts screaming like a little girl and wailing his arms about trying to scare away a couple of bees. We all tell him to STOP wailing his arms about because that will do nothing but rile them up and CAUSE him to get stung. He continues crying like a little girl and wailing his arms until the bees fly away. We're making fun of him for crying like a little girl and he's just making excuse after excuse of him being "allergic" to bees. We keep telling him that is all the MORE REASON to SIT STILL and not to RILE THEM UP. A half an hour or so passes and I go to pick up my can of soda and drink from it. I dang near swallow three bees and I calmly spit out my soda and all three bees along with it. The little girl starts touting "I told you so's" and claiming he made his point, that we should be careful when bees are around because I almost just swallowed three of them. I turn to him, No, you're missing the bigger picture, I just made my point, I was calm and didn't start jumping up and down and wailing about, and guess what, I DIDN'T GET STUNG!

True dat. The only time I really use them is when users post a link on the forum for a web site they are having issues with. I'll right-click their link and open in an Incognito window instead of setting temporary rules in NoScript, uMatrix, and Tampermonkey.

Until you open the Developer Tools in an Incognito window, if I remember correctly.

Hit F12 then hit F1 and then click the second entry in the first dropdown - that will put the console in English (I forbid fonts installing so my screencap will only show "squares" for fonts I can't read to begin with). v13.5 doesn't always "remember" this setting. I personally don't use any version higher then 13 build 2206 because all newer builds save settings in the same location that telemetry is stored. v13 build 2206 and OLDER is easier to prevent telemetry.

It's funny that some people will never open their web browser in a "maximized" window and tout that as a privacy concern, but yet they will run web-gl or web-rtc and those are both a thousand times worse than a web site knowing what your screen resolution is.

When you launch 360Chrome, immediately hit F12 then open the Network tab. Maybe some of your extensions are doing some downloading/uploading behind your back. Or use something like DNSQuerySniffer or TcpLogView (both from NirSoft) to see if you have some unexpected network traffic.

I just noticed something! @Dave-H can EDIT his posts WITHOUT the post adding the "Edited <time> ago by Dave-H" footnote. Thankfully I already had the post "quoted" before the Ignoring the spelling error (it should be writeable) was EDITED OUT without the "Edited <time> ago" footnote added when that EDIT was made. Caught you, Mr. Dave-H. In other news, the spelling error first pointed out by Dave-H is not actually a spelling error. Google, Bing, and DuckDuckGo will all flag "writeable" as mispelled but accepts "writable" as properly spelled.

Hmm, not seeing that here. Are you using anything special as your startup tab in Settings -> Basics -> On Startup ?

(not to go all-caps on you, but...) LOL