Major theme glitch on PM26 with Windows 10

[Channel 2012]

Whew, I'm glad I only updated my portable browser which only gets used with Windows 7. Did anyone test this thing?

When the window is not maximized, it is halfway okay, but the minimize/maximize/exit buttons area is all white and weird looking and everything goes colorblind below the titlebar:

When the window is maximized, the whole thing goes gray (except for the buttons turning white as when the window is not maximized) and the text becomes unreadable. The transparency and trim color disappears completely:

These bugs were found using the original 10240 build of Windows 10 x64 and the portable Pale Moon x64 (haven't dared to try updating any of the others after this mess). Windows 10 is running pretty stock with the exception of the patches that fix the visual style (custom fixed visual style and Glass8). Just thought I'd throw this out there to the design team. This is a major bug.

[Lootyhoof]

Not a bug. If you use the default Windows theme (since it appears you're using a third-party theme) it appears correctly; the white background is only there on non-default setups like yours, to ensure that the caption buttons are still viewable.

Did anyone test this thing?

Yes, that's why this appears as it does. Try this in userChrome.css:

Code: Select all

.titlebar-button:not(:hover):not(:active),
#main-window {
  background-color: transparent !important:
}

We can only test on the default visual style, after all, so you're on your own with third-party ones.

[Channel 2012]

Not a bug. If you use the default Windows theme (since it appears you're using a third-party theme) it appears correctly; the white background is only there on non-default setups like yours, to ensure that the caption buttons are still viewable.

Did anyone test this thing?

Yes, that's why this appears as it does. Try this in userChrome.css:

Code: Select all

.titlebar-button:not(:hover):not(:active),
#main-window {
  background-color: transparent !important:
}

We can only test on the default visual style, after all, so you're on your own with third-party ones.

I think of it less as a "third party" or "non default" theme and more of a restoration to how it is supposed to look. As for the user chrome, I'll give that a try, but I cannot find it on the copy of Pale Moon portable that I'm using for testing. Does the portable version name it something different or put it someplace else?

Update:
Figured out the user Chrome (it was just a matter of creating the "chrome" folder and the "userChrome" file). From here I was able to learn about and experiment with the file. The code you provided had no effect, but when combined with other hints found around the forums, I was able to produce a couple different results.

Using this...

Code: Select all

#main-window[windowtype="navigator:browser"] {
background-color: transparent !important;
}

I got this:

Combining that with your suggestion, I created this:

Code: Select all

.titlebar-button:not(:hover):not(:active),
#main-window[windowtype="navigator:browser"] {
background-color: transparent !important;
}

This kind of fixes the buttons, but overlays them with redundant black shapes as pictured here:

The artifacts disappear when hovering over the icons, but they are colored wrong when being hovered over. They turn a solid blue instead of a subtle blue (in the case of minimize and restore) and solid red (in the case of exit).

Can anyone see any mistakes in my new userChrome file that could be causing the redundant icons?

[bigjohns]

It's windows10, not you or me or the theme... Microsoft borked up so much of the visual stuff in WIN10 I'm surprised anyone can even say they like it. meh.
As you said you're using glass8, etc. to make it look normal and usable...

[Channel 2012]

It's windows10, not you or me or the theme... Microsoft borked up so much of the visual stuff in WIN10 I'm surprised anyone can even say they like it. meh.
As you said you're using glass8, etc. to make it look normal and usable...

You're absolutely right about Microsoft; they screwed it up big time. The only reason I use Windows 10 at all is because of the enhanced support for high-density monitors (and for some of the other handy/convenient improvements held over from Windows 8 and 8.1). However, the point is that prior to version 26, Pale Moon was working just fine alongside Microsoft's screwups and the community's theme patches, so I know that they have the know-how to make it work properly in Windows 10. If these glitches don't appear on Windows 9, 8, 7, or Vista, could a development hack be programmed in to make Pale Moon operate in "legacy mode" just for Windows 10?

[Moonchild]

Windows 10 required that we completely re-do our theming of the title bar and controls. Windows 10 also does not have transparency in its windows unless you force it (e.g. with a 3rd party tool), but we cant be expected to cater to that kind of setup out of the box.
The window controls on Windows 10 in Pale Moon 25 were an absolute disaster (incorrect shape and half cut off etc.) and this system control layering could not be repaired otherwise.
Not only that, another problem with Windows 10 is that Microsoft is making "rolling updates" in which these things are changed out from under us, after being established in RTM after a long beta period in which developers like us HAVE to make a choice to align custom theming with some time point for a first release.

A simple workaround will be, however, to tell Pale Moon to use full system window theming. How? Enable the classic menu bar instead of the Pale Moon button.

[Channel 2012]

Windows 10 required that we completely re-do our theming of the title bar and controls. Windows 10 also does not have transparency in its windows unless you force it (e.g. with a 3rd party tool), but we cant be expected to cater to that kind of setup out of the box.
The window controls on Windows 10 in Pale Moon 25 were an absolute disaster (incorrect shape and half cut off etc.) and this system control layering could not be repaired otherwise.
Not only that, another problem with Windows 10 is that Microsoft is making "rolling updates" in which these things are changed out from under us, after being established in RTM after a long beta period in which developers like us HAVE to make a choice to align custom theming with some time point for a first release.

A simple workaround will be, however, to tell Pale Moon to use full system window theming. How? Enable the classic menu bar instead of the Pale Moon button.

So there's no chance that it could be brought back to the way it was working in version 25 just for Windows 10? The thing is that it was working 100% fine before version 26, so why not just leave it how it was?

[Moonchild]

The thing is that it was working 100% fine before version 26

No, it wasn't. It was broken.

[Channel 2012]

The thing is that it was working 100% fine before version 26

No, it wasn't. It was broken.

But it isn't. I'm using version 25 right now and it is 100% perfect in Windows 10 whether maximized or not (at least as far as I can tell).

[Zod5000]

The thing is that it was working 100% fine before version 26

No, it wasn't. It was broken.

But it isn't. I'm using version 25 right now and it is 100% perfect in Windows 10 whether maximized or not (at least as far as I can tell).

It's not just you. I had no problems with version 25, windows 10, and aeroglass either. The problem instantly started with 26.

I know technically the palemoon team doesn't support aeroglass (also called glass8) but I think it's the only (or by far the most popular) program to reenable transparency in windows 10. I would think it's common enough to try and support it? Modifying usechrome mostly fixed it, but I also get those artifacts on the minimize,maximize, close buttons.

[Channel 2012]

The thing is that it was working 100% fine before version 26

No, it wasn't. It was broken.

But it isn't. I'm using version 25 right now and it is 100% perfect in Windows 10 whether maximized or not (at least as far as I can tell).

It's not just you. I had no problems with version 25, windows 10, and aeroglass either. The problem instantly started with 26.

I know technically the palemoon team doesn't support aeroglass (also called glass8) but I think it's the only (or by far the most popular) program to reenable transparency in windows 10. I would think it's common enough to try and support it? Modifying usechrome mostly fixed it, but I also get those artifacts on the minimize,maximize, close buttons.

I would think it would make sense to test with the patches installed too. Like I mentioned earlier, it's not some wack-o third party wild and crazy theme or anything; the Glass8 and other fixes simply patch the operating system back to how it is supposed to be. I suspect Pale Moon has competent developers who can get to the bottom of this, so I'll hold off for a few months and give them a chance to get this fixed. In the meantime, (and I never thought I'd ever say this) I've already started testing Google Chrome, which has come a long way since the last time I tried it.

[megaman]

Channel 2012, please don't use quotes excessively, trim it down to one sentence or a few.

[Moonchild]

I would think it would make sense to test with the patches installed too.

You think we don't test the browser before releasing...?

it's not some wack-o third party wild and crazy theme or anything; the Glass8 and other fixes simply patch the operating system back to how it is supposed to be.

It's a wack-o third party wild and crazy tool that makes the operating system behave differently than expected.
And "how it is supposed to be" is up for debate. It's "how you prefer it". Do you really think we can go and try to cater to all the endless possibilities of people using skinning and system modification tools that float around? It's impossible, and I don't even want to think about the silly amount of extra work you expect us to do for that. We already have to make sure Pale Moon's universal interface works on all Windows versions ranging from XP to Windows 10, you can't reasonably expect us to extend that with configurations that external tools change.

It seems a common topic these last few days. But basically: if you hack your OS, and run into issues because of it, then we can't provide you with any sort of support or solution. You broke it, and you'll have to fix it. There is also no "but..." beyond this point.

[Channel 2012]

I would think it would make sense to test with the patches installed too.

You think we don't test the browser before releasing...?

Yes.

It's a wack-o third party wild and crazy tool that makes the operating system behave differently than expected.

I have to disagree with you on that one. It makes the operating system behave properly and as expected.

Do you really think we can go and try to cater to all the endless possibilities of people using skinning and system modification tools that float around? It's impossible, and I don't even want to think about the silly amount of extra work you expect us to do for that.

I don't expect anyone to do anything special for any unusual setup. The point is that it was working just fine before. Every version of Pale Moon before 26 (that I've tried anyway) work pretty much perfectly on Windows 10.

We already have to make sure Pale Moon's universal interface works on all Windows versions ranging from XP to Windows 10, you can't reasonably expect us to extend that with configurations that external tools change.

No. You had Pale Moon's "universal interface" working on all versions of Windows from XP to 10; now with version 26, it only works on XP-8.1. Would it be that difficult to just exchange the buggy UI code for the tried-and-true system that had been working fine with every version of Windows before?

[New Tobin Paradigm]

A bunch of stuff.

How about this.. Patches Welcome.

Moderator Note: Topic Locked to prevent escalation.