bigmuscle

try this in "c:\Users\xxx\AppData\Roaming\Mozilla\Firefox\Profiles\yyy.default\chrome\userChrome.css" /* * Do not remove the @namespace line -- it's required for correct functioning */ @namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"); /* set default namespace to XUL */ #main-window { background-color: transparent !important; -moz-appearance: -moz-win-glass !important; } #toolbar-menubar, #titlebar, #tabs-toolbar { -moz-appearance: none !important; background-color: transparent !important; }

I use this in c:\Users\...\appdata\Roaming\Thunderbird\Profiles\.....default\chrome\userChrome.css /* Set the default namespace to XUL */ @namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"); #messengerWindow { background-color: unset !important; } #titlebar, #titlebar-content, #titlebar-spacer { background-color: transparent !important; } .titlebar-button { opacity: 0.25; transition: background-color 0.2s ease; } .titlebar-button > .toolbarbutton-icon { list-style-image: none; }

I wanted to try but unfortunately I have not Win8.1 installed anymore so I cannot test it. Is there something in the debug.log (with verbose logging enabled) ?

I'm not sure if I correctly understand you. But moral obligation for what? Doesn't the software presented on my website work correctly on the stated version of operating system? Or do you think that the software developer is responsible for the situation when an user installs an operating system version that has never been claimed to be supported?

Phenix: read the last Q&A here http://glass8.eu/guide

If someone installs the Aero Glass into Program Files, it is only his problem that it is not able to download and store the symbols. It has been said milliontimes that it mustn't be installed there and even the guide mentions "Important thing is that you must place all files in writable location (i.e. not in Program Files),, because DWM process does not run under user's credential. If you don't do this, Aero Glass will not be able to download symbols". Also the note about debug.log "if the verbose logging is enabled" was not probably too bold and underlined.

I think that I already wrote it some time ago, but the Microsoft implementation of the symbol downloading (symsrv.dll) has the bug if the download fails once for whatever reason (mostly internet connection failure), it will fail forever even the reason has already gone away. Thus I recommend to delete "Symbols" folder and try again... especially if there is download.error file somewhere. Also, the real reason of the failure can be found in debug.log if the verbose logging is enabled.

Fine, I was able to reproduce the problem using the remote desktop, so let see if it helps to fix it

It is Firefox bug that it does not accept system settings but always tries to imitate Win10 UWP appearance. You can tweak this behaviour by userChrome.css file, but the result will never be 100% correct. Example can be found here: https://github.com/Aris-t2/CustomCSSforFx

Yes, these versions should be correct if you have 64-bit versions of both DLLs. The exact reason of symbol failure can be found in debug.log if verbose logging is enabled.

Do you have correct symsrv.dll and dbghelp.dll?

I would help and fix it but I don't see such issue on any of my computers. Does it happen in some specific situation? Multiple windows, UWP app window in way or something special?

And? Does it say anywhere that it should happen? That Aero Glass should load something into control panel? You are free to fix it, but I understand that it is much easier to complain about other's work. Sure... really "many bugs" Again, you are free to do it :-P It was dropped to make a room for you to do it. Now, you have a chance to do better Aero Glass than me. This project was never meant to be profitable. But you should start working on your own Aero Glass now, so it is ready when I leave the project. But no, you will not do it, because you rather complain about other's work. If I leave, you will complain and then you move to some another project to complain...

Then, you should not be too lazy and create your own Aero Glass software instead of complaining about so-called bugs which have absolutely no relation to Aero Glass and have never been promised to be the part of my Aero Glass software.

I'm aware of this bug, I'm just not sure if it is easy to fix.

If you are not the advanced user then you should not use any experimental software.

Aero Glass does not render titlebar buttons so it cannot influence it in any way. The glyphs are stored in the used theme for several DPIs. If they are rendered incorrectly then you are using either uncommon scaling or invalid theme.

Login on the website and then you can download the UNSTABLE DEBUG version.

Don't afraid. It was just an ironic note, because of users asking the same things over and over again and they still expect some answer although it has been covered milliontimes.

Never.

Nope, Aero Glass does not interfere with the fluent design. Only applying DWM frame on UWP apps does (regardless the Aero Glass) - which can be disabled anytime.

Nope, it is still disabled, because I don't know how to deal it since applying DWM frame on UWP apps will break fluent design.

you can change BlurDeviation settings

ApplicationFrame hook is intentionally disabled in RS3 builds.

He is probably funny. But I see much more funnier when someone installs buggy beta version of the operating system and then he complains that he is not able to run the software which was never meant to be run there.