NotHereToPlayGames

On my XP x64, the --no-sandbox option seems to require an additional 13 MB of RAM.

Bummer. How often would you say the disappearing fonts occur (I have witnessed disappearing fonts but I haven't witnessed for well over two months)? Once every hour without --no-sandbox? Opposed to once every three weeks with --no-sandbox?

Do you happen to have a consistent repeatable scenario that causes the disappearing fonts? Something like it "always" happens in Site F each and every time you have Sites A, B, C, D, E, F, G, H, and I open?

Depending on your definition of "manager" -- I "manage" all of my passwords by using an "auto-fill" extension (I disable 360Chrome's Personal Data settings for saving passwords and autofill). I use Autofill version 10.3.4 -- https://www.crx4chrome.com/crx/303031/

The problem is that Chrome (and Firefox) DOES NOT USE YOUR WINDOWS SETTINGS (when your Windows says to NOT "smooth fonts"). Chrome decides for itself what fonts do or do not require anti-aliasing. Firefox decides for itself what fonts do or do not require anti-aliasing. And Chrome and Firefox do not agree with each other as to what fonts require anti-aliasing. But Chrome (and Firefox) DOES USE YOUR WINDOWS SETTINGS to determine what METHOD to use for "font smoothing". Perhaps YOUR best solution is to forget about seeking to resolve this at the browser level for both Mypal and for 360Chrome. But rather seek out an OPERATING SYSTEM REPLACEMENT for "font-smoothing" IN ITS ENTIRETY.

There is an about:permissions page. But no setting for microphone. NM28 is probably "supposed to" popup a little dialog box when a website requests mic access but it does not (my reference page is Google Voice).

The disappearing fonts has been mentioned in the past. Does not seem to plague every user. I myself only witnessed it with "new" versions of Stylus. I've never witnessed it once I dropped down to Stylus version 1.5.15. I do not use the --no-sandbox option. Unsure of the pros and cons of --no-sandbox.

You may have to do what pretty much everybody here at MSFN does - keep a handful of browsers at your disposal and use this one for these tasks and that one for those tasks. You will NEVER get Firefox/Mypal and Chrome/360Chrome to behave identically - NEVER. They are entirely two different beasts and they do things entirely different from each other.

Are you saying that this XP setting WORKS for you in 360Chrome but you do not want to use it for other XP reasons?

The ONLY other option as I see it (in XP) is that you will HAVE TO learn how to use Stylus extension. Firefox-forks AND Chromium-forks both do antialised fonts regardless of your Operating System telling it not to. The only difference is what font-families will be antialised in one versus the other.

How do I set a permission to allow mic access to a given web site in NM28?

Sweet! Ecstatic to report that "invalid identity escape in regular expression" has been resolved somewhere between NM28 28.10.6a1 (2022-10-27) and NM28 28.10.6a1 (2023-01-13). I'll narrow it down a bit more precisely one of these days as I haven't been keeping track with weekly changelogs. This one solitary error has been my holdup for a couple of years as far as returning to NM28 as my default. I may no longer need 360Chrome at all anymore. Though a rebased 360Chrome v13.5 now uses less RAM than NM28. I haven't tweaked NM28 and tested on all my websites, but it is very good news as far as "invalid identity escape in regular expression".

Agreed. edit - but it's anybody's guess as to how much longer v86-based will render "modern" web sites.

Did you try the XP Display Setting of Standard for font-smoothing? That's pretty much the only fix I am seeing aside from resorting to case-by-case Stylus sheets.

This is true 100% of the time. There is a 50% chance that today's weather will be exactly like yesterday's weather.

Doesn't that make you afraid of drowning instead of afraid of water? When a waitress walks around with a pitcher of ice water to refill your glass, do you hide under the table and tremble in fear? waka waka waka Kind of like not being agraid of heights but being afraid of falling and hitting the pavement. If I had half a million lying around, sure, I'd go for it.

Not necessarily. There are some weather sites that have radar and maps that require WebGL, which I disable by default in my releases. So yes, weather questions are allowed as some users may not know how to enable WebGL.

"Cheaper than a condominium" - article cites "less than 500,000 euros. Nowhere my definition of "cheap", lol. 500,000 euros is roughly $541,500.00 US Dollars. ie, over half a million. I'll have to pass Oh, and would the island have electricity and internet service?

I'm not well-versed in those types of changes but have experimented with them several months ago. Some of those types of Chrome flags also require hardware acceleration (which does not work in XP even if you set the setting to use it). There are flags which affect Skia subpixel positioning when running "headless" (don't know what "headless" is). --font-render-hinting Sets font render hinting when running headless, affects Skia rendering and whether glyph subpixel positioning is enabled. Possible values: none|slight|medium|full|max. Default: full. A full list of Command Line Switches - https://peter.sh/experiments/chromium-command-line-switches/

With the XP's Standard method, I don't notice any "global" non-crisp fonts. Can you demonstrate via screencap? Upon limited research via internet searches, it seems that both Firefox and Chrome still antialias "some fonts" REGARDLESS of XP being set to NOT smooth font edges (which the PM'd web site clearly demonstrates). The difference is "what" fonts they BOTH deem as fonts which require antialiasing - font-family A will be antialiased in Chrome but not in Firefox, while font-family B will be antialiased in Firefox but not in Chrome, and font-family C will not be antialiased in either. And that forcing "Standard" (clear and crisp to me) or "ClearType" (which looks TERRIBLE to my eyes) is the only way for a "universal" (all apps) font rendering, font-family A, B, and C identical in app X, app Y, and app Z.

My hunch was that the BSODs were caused by pushing the envelope on RAM consumption. Before we rebased, it was not uncommon for 360Chrome v13/v13.5 to consume 90+% of my RAM on my 4 GB RAM XP x86 (but no BSODs) whenever I opened half a dozen tabs or so. But I've yet to ever see even 50% of RAM being used now that it's been rebased (still dislike the very very long launch time for first launch after system hibernate but have decided to accept as-is).

My setup IS using font smoothing. It uses STANDARD method instead of ClearType method. ClearType gives me migraines because there are red and green "dancing pixels" in every corner of every letter that triggers migraines for me (among others, was very big in tech news back when Vista first came out).

Nope. But I hope answering your question isn't "stalking". My apologies for overstepping. Not to make excuses, but my doctor took me off caffeine on Monday. Getting old sucks, lol. My bookmark is the "unread content" link, so I kinda reply to anything and everything, there is no "stalking", but ACTIVE THREADS that have a higher chance of pulling me in over time, lol. But anyway... Sipping my hot apple cider. Still no replacement for my long-loved Mountain Dew.

DirectWrite disabled resolves that font issue in my Win7. But agreed, no change in XP. That font issue is resolved on my end via - Right-click on My Computer and select Properties. Go to the Advanced tab and click Settings under Performance. Make sure that the Smooth edges of screen fonts is selected. Click Apply if you had to select it because if was previously unselected. Click OK to close out of those and that web page should now display fonts correctly. Unsure if this is also required, but I also have this option set. Right-click on empty space on the desktop and select Properties. Select the Appearance tab then select the Effects button. Under Effects, I use the Standard method for screen fonts and NOT the ClearType method. Much cleaner - Hope that works for you also.