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.

11 hours ago, NotHereToPlayGames said:

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

Yes, I am. The key needs to be purchased for 10 000 Canadian dollars or so, it was explained by the win32ss in the issues thread. I'm sorry, I won't browse through 16183218318 pages of issues. But you're very welcome.

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.

5 minutes ago, D.Draker said:

I won't browse through 16183218318 pages of issues.

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

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.

10 hours ago, NotHereToPlayGames said:

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.

Not only that, he made the whole browser light up like the X-mass tree. Look at the shadows near "about".

16 minutes ago, Saxon said:

Look at the shadows near "about"

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.

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.

31 minutes ago, Saxon said:

he made the whole browser light up like the X-mass tree

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).

30 minutes ago, NotHereToPlayGames said:

Not sure how detailed of a Mouse Hunt this is going to become

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"...

Edited March 16, 20251 yr by NotHereToPlayGames

@NotHereToPlayGames, fix your monitor!!!!!!!!!!!!

Browser on the right has proper white colour.

13 hours ago, NotHereToPlayGames said:

It's a FONT RENDERING ISSUE, not a brightness issue. 

I think Saxon meant the shadows around Google Chrome tile. 

14 hours ago, NotHereToPlayGames said:

So yeah, evidence that the Supermium developer did change the color of an INACTIVE WINDOW.

Eureka! It happened. Now, that's what I was trying to explain to you. He increased overall brightness, and light grey coloUr simply became overblown to white. Got that?

5 hours ago, D.Draker said:

@NotHereToPlayGames, fix your monitor!!!!!!!!!!!!

Browser on the right has proper white colour.

I lide the grey color, defalt and white are too bright...

Edited March 17, 20251 yr by hidao

5 hours ago, D.Draker said:

fix your monitor!!!!!!!!!!!!

"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...