NotHereToPlayGames

That's the 2nd person to claim I have a Dell 2407. I do not! But nice try. My mistake for not correcting the 1st person, I suppose. I forgot how close-nit the "posse" is.

NOT TRUE !!! I have used and you and I are as opposite as opposite can be on Vista - IT IS BY FAR THE UTMOST WORST OS I HAVE EVER USED !!! Post your "complaint" regarding Supermium AT GITHUB. And I'll be the first to "laugh out loud" when the developer replies no color has changed. Changing the tab bar color is one thing, THAT IS NOT WHAT YOU KEEP COMPLAINING ABOUT, you "all" keep complaining about overall brightness and font issues. THIS IS A DEAD END. Not relevant! Brave is by far the most BLOATED browser I've ever ran across! I've had to axe out more out of Brave than I've ever had to axe out of 360Chrome! You have to compare to "virgin Chrome". THEY ARE REVEALED IN THE DEV TOOLS CSS DECLARATIONS. I CANNOT FIND ANY CSS COLOR CHANGES. AND NEITHER CAN YOU OR YOU WOULD POST A SCREENCAP OF DEV TOOLS AND PROCLAIM "TOLD YOU SO". YOU HAVE DONE NO "TOLD YOU SO" BECAUSE YOU CANNOT FIND ANY CSS COLOR CHANGE. Q. E. D. THIS IS A DEAD END. THIS IS A DEAD END. THIS IS A DEAD END. Done... Toodles... This has become nothing but a gigantic CIRCLE JERK... Contact GITHUB...

No luck. I can pass Widevine "tests". Netflix even "sees" that I have Widevine installed. But Netflix requests "protected content" settings that I have already set but Netflix/Supermium isn't working. So I've made it three steps in but have one more step to go.

Read the whole thread. Too many folks keep speed-reading and jumping over the important parts. The INACTIVE WINDOW is light gray. But that light gray in Official Chrome is changed to BLUE in Supermium. The "offense" is that a light gray is changed to (and I *quote*) "piercing white". Blue does not equal "piercing white", SO THE INACTIVE WINDOW (TAB BAR) IS *NOT* THE "OFFENSE". By all means, ask the developer himself. He's going to tell you the same exact thing that I've already told you - NO COLORS HAVE BEEN CHANGED. Font rendering has been changed, but that is NOT what is being "complained about". Until we find proof in a CSS DECLARATION, then you "dark mode" folks can keep running in circles all you want (none of you use Supermium anyway). I, on the other hand, have a vested interest in Supermium. I need a PORTABLE chrome-based for a laptop being set up for streaming. Some have had success with Supermium+Widevine, others have not. I'm still in-process.

Can you please explain how this is done? I trial-tested Supermium v132 R1 (newest) over the weekend and manually included Widevine files from Official Chrome v132. An online Widevine Test ( here ) indicated that Widevine is installed but the Widevine Test reported some "key" error (forget the wording). All I got on the Supermium thread was a claim that DRM is not supported and by a person unaware that the Supermium developer includes a Widevine patch. I currently have no use for Supermium without Widevine, but it is my PREFERENCE (over Brave and the d@mn embedded adblock and bitcoin cr@p) for the streaming-only laptop I wish to deploy it on. Any advise on HOW to get WIDEVINE to function in Supermium is greatly appreciated. Would prefer v132, but if I have to drop to v126 then that should be fine for my needs (probably should have tried it over the weekend, didn't dawn on me at the time).

THINK ABOUT IT !!! If we are to "report" something to GitHub and "claim" that a color changed, THEN IT IS ON US TO FIND THE RGB/COLOR CHANGE WITHIN THE CSS DECLARATIONS !!! Then, AND ONLY THEN, can we ask the developer, "Why did you change RGB (a, b, c) to RGB (x, y, z)?"

WHERE ??? The *only* light gray discussed thus far is the INACTIVE WINDOW TITLE (TAB) BAR which changed to a blue that is darker than the ACTIVE WINDOW TITLE (TAB) BAR. Seriously, how can we report on GitHub if none of us are even on the "same page" - WHAT LIGHT GRAY HAS CHANGED TO "PIERCING WHITE" ??? ??? ???

You really do have to COMB THROUGH the CSS differences instead of always always always trying to blame the monitor. Gets Old and shows ignorance!!! These are screencaps which capture pixel colors *BEFORE* the monitor "renders" them! These are not pictures taken with a camera which would show pixel colors *AFTER* the monitor "renders" them. Take two monitors side-by-side, set one brightness at 100%, set the other at 5%. Screencap same image on both. The screencap/print-screen reveals pixel colors that are IDENTICAL. A *camera* would reveal the brightness setting differences, a *camera* would reveal "bad caps" on one monitor relative to the other, et cetera. THERE ARE CSS DIFFERENCES BETWEEN SUPERMIUM AND OFFICIAL CHROME. DIG THROUGH THEM IF YOU REALLY WANT TO FIX *YOUR* BRIGHTNESS ISSUES. I SHOULD NOT HAVE TO FIND THEM FOR YOU!

"F U"... It is *NOT* a monitor issue !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! Font rendering... Font rendering... Font rendering... Font rendering... Font rendering... Font rendering... Font rendering... Font rendering... Font rendering... Font rendering... Font rendering... Font rendering...

No more for me. Everything shows *IDENTICAL* for me (anti-aliased font difference YES, *expected*, color brightness difference NO)! I'll let you "dark mode" folks fight over this one. And fight... And fight... And fight... My VMs are closed for the day. Supermium targets pre-10 so that font may likely not even be Segoe UI whereas Official Chrome would be. As this really does come up *ALL THE TIME*. Kind of gets old, in my not-so-humble-opinion. I've shown side-by-side out-of-the-box, nothing more I can do, some will always see what they want to see, hear what the want to hear. It's a FONT RENDERING ISSUE, not a brightness issue. THERE IS A DIFFERENCE. It's called "sub-pixel" rendering. Moving on now... "Toodles"...

Not sure how detailed of a Mouse Hunt this is going to become, but Supermium and Official Chrome both have the same EXACT background color on the settings page (RGB = 255, 255, 255).

In Official Ungoogled (because that's the one I have open at the moment), that "about" is SEGOE UI font family. That is a font that SUCKS TERRIBLY in everything pre-10. That font gives me migraines in win7 but is fine in win10. OS's have a very unique-unto-itself way of rendering that font. Cleartype tuning is all but a must to get that font to "look right". I would NOT expect it to render the same from one system to the next.

That is a font-rendering issue. Supermium should look different because it is one of very few browsers still using GDI font rendering. I do not know its default state. I would not be surprised if fonts are effected with GDI enabled *AND* with GDI disabled. As the whole browser's font-rendering scheme is no longer apples-to-apples.

Supermium inactive blue is a darker blue (backwards to all of my other apps, active is generally darker than inactive, another reason I have my own theme). Official Chrome, on the other hand, has a light gray for inactive (probably the same light gray as Brave, did not compare directly). So yeah, evidence that the Supermium developer did change the color of an INACTIVE WINDOW.

lol, me neither. I just assumed that Supermium could run Widevine (required for my Netflix but my other streaming providers work without Widevine).

Supermium active color is EXACTLY THE SAME as Official Chrome active color. RGB = 211, 227, 253. EXACTLY THE SAME !!! Personally, I *hate* this pale puke-blue. Your "brightness issue" really is not the developer's concern, in my not-so-humble-opinion. The blue is the EXACT SAME as upstream, the developer made no changes.

Default out-of-the-box Brave has no blue. Active Window and Inactive Window are both light gray. With active having text and buttons "more black" than inactive. So I'll compare Supermium's out-of-the-box blue to Official Chrome's out-of-the-box blue.

For the record, I've given up on trying to keep up with all of your "brightness complaints". They pop up ALL THE TIME and I stopped following if the complaint is a button on a web site being rendered this way or that way or if the complaint is a blue color (correct spelling, I'm allowed to use US spelling even if folks around here think everybody should use non-US spellings, but I digress). One moment, I'll load up two brand new VMs that have never seen Supermium or Brave and do a side-by-side color-check.

Will see what I can do. Until this morning, I've never actually used Supermium outside of a VirtualBox VM. So the host-OS Supermium *must* be tied to my all-fork profile. It's just how I use my browsers, ZERO interest in maintaining several dozens of profiles.

Are you sure? Then why are there these two files included in v132? Unsure if these are included in older versions. And the Widevine Test does *SEE* that the Widevine files are present, but it fails some "key" check, forgot the wording offhand. widevine_patch.exe and win7_fixwidevine.cmd

Has anyone using Supermium on Win10 been able to pass a Widevine Test such as this one ? I'm assuming that I am overlooking something simple.

Also, upstream v135 or so (ie, only us 10 or 11 users have seen it in action) now has an option to NOT USE chrome's color scheme but use the OS COLORS instead! But it will take several MONTHS for these upstream changes to trickle down to all of the forks.

No clue. Upstream changed the title bar colors around v126 or so, forget exactly. My profiles in everything from Brave, to Supermium, to Ungoogled, to regular Chrome all use my own theme that works in all of them and reverts to the same title bar colors used in XP. I cannot really test without undoing my profile. I use the same EXACT profile in ALL of my Chrome-based. As long as I always go UP a version or two instead of down, I've never had any issues.

What blue and where?

This is "only" a Dark Mode Issue, in my not-so-humble-opinion. I have no problem whatsoever with Supermium in "normal mode".