windowblind NUKED my firefox UserChrome.css file!!!

major issue how windowblinds replaces files without a warning.

so i saw nice looking windows 7 aero theme on the web and downloaded it and installed windowblinds for it.

but unlike the rest of my apps that chanced immediately as the theme got applied, firefox did absolutely nothing.

so i typed about:restartrequired and did restart of firefox, and to my horror my customized ui like tabs not on top and other similar stuff was gone.

why is that? because your software didn't bother to think that if user has chrome folder, userchrome.css file inside that folder and firefox is set to use said css file by setting about:config -> toolkit.legacyUserProfileCustomizations.stylesheets -> thrue

that maybe they already had some settings there that they WANTED TO KEEP!!!

lucky for you that windows file backup utility was able to restore recent enough version of that userchrome.css file that firefox started to work again.

how hard it is to make that tool to check if user already has chrome folder inside C\Users\*****\AppData\Roaming\Mozilla\Firefox\Profiles\

then create at least a copy of the userchrome file that you are in the process of ruining. such check should not be that hard.

 

needless to say, that i'm not going to be purchasing a license for this app after such experience, but this kind of check is such basic thing compared to the rest of this app that this should be added soon as possible.

 
12,084 views 12 replies
Reply #1 Top

Hello,
Sorry to hear you are having issues. Not really sure what you mean by that "userchrome.css" thing. But you simply need to have Firefox's Title bar enable as mentioned right there in that red box, follow the red arrow.


Basj,
Stardock Community Assistant.

Reply #2 Top

https://1drv.ms/u/s!AvZMCSY-sx7UhpU971U1uS1lmuGDfA?e=u9avtk

there is how my userchrome.css style file looked like BEFORE i installed windowblinds and off course as you can see from this screenshot https://1drv.ms/u/s!AvZMCSY-sx7UhpVAPpvRrxqREoy3Uw?e=ka9Aog i also had the firefox titlebar enabled.

also this issue is not about if the windowblinds enabled the windows 7 styled titlebar or not. this was about how it nuked the whole browser styling.

Reply #3 Top

Have you tried the solution I listed above?

Thank you,

Basj,
Stardock Community Assistant

Reply #4 Top

https://1drv.ms/u/s!AvZMCSY-sx7UhpVCI_NngDlXIwNx9g?e=HMamwx

there is the link to the userchrome file after applying https://www.deviantart.com/newinfinitepro/art/Aero7X-Reset-for-Windowblinds-10-836337064 this theme on my machine.

i'm not sure if this is something that this theme specifically did, or if these changes happen regardless of the theme used.

in any case it is poor way to do this, if this is something you feel your app NEEDS to do, then at least first do automatic copy of the old userchrome.css file.

Reply #5 Top

Quoting basj, reply 3

Have you tried the solution I listed above?

Thank you,

Basj,
Stardock Community Assistant
End of basj's quote

Reply #6 Top

Quoting basj, reply 3

Have you tried the solution I listed above?

Thank you,

Basj,
Stardock Community Assistant
End of basj's quote

 

i try to stay polite here and so don't really say what i would like...

but anyway did you even read my post or looked at the screenshot i posted?

my issue wasn't that the firefox titlebar remained solid, my issue was that the whole firefox ui got nuked because your app replased my userchrome.css file!

Reply #7 Top

I don't really think, Windowblinds can do that. But, just to be sure. I have forward your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Reply #8 Top

Firefox with ruined ui

i tried with that "allow windowblids to skin firefox titlebar" turned on and off and all that changed was that the titlebar indeed changed from solid windows 10 looking to that windows 7 one.

but the actual issue never changed. no matter if that setting was on or off, when applying a new theme that userchrome.css changed to that modified one.

so my firefox looked like it does on the picture above, and with my theme that ui just doesn't work at all.

i also tested out if turning toolkit.legacyUserProfileCustomizations.stylesheets on about:config to false (basically turning off the whole userchrome.css support) and after restarting firefox, the title bar remained themed to the windowblinds windows 7 themed one.

so is there even a valid reason to touch that file.

at the very least your app should check if userchrome.css is present on the system or not, then notify user about that the app needs to modify that file and also do automatic copy of that file in the same folder before modifying anything on it.

so after applying the theme there should be both the userchrome.css that you have mutilated  and the original as a userchrome.css.bak or something like that.

Reply #9 Top

WindowBlinds will indeed replace the userchrome.css file in order to workaround an issue in Firefox with as I recall how it paints inactive tab text.  It may be Firefox has been fixed since WB worked around the issue in which case we can remove that from future WB updates.

However it will backup the original to WBbackupuserChrome.css in the same folder so I am unsure why that has not happened and can only say sorry that it did not.  Thankfully you were able to get the original back.

You can put your own CSS into ff.css which is stored in the WindowBlinds installation directory and it will be copied in instead.

 

Reply #10 Top

i went through the chrome folder and there is no trace of that backup file anywhere, also as i said turning toolkit.legacyUserProfileCustomizations.stylesheets to false in about:config stops firefox to see any kind of userchrome files at all.

but even with that turned to false, i saw no difference on how firefox titlebar looked when using windowblinds theme, after restarting firefox.

Reply #11 Top

Quoting hinukmattila, reply 10

i went through the chrome folder and there is no trace of that backup file anywhere, also as i said turning toolkit.legacyUserProfileCustomizations.stylesheets to false in about:config stops firefox to see any kind of userchrome files at all.

but even with that turned to false, i saw no difference on how firefox titlebar looked when using windowblinds theme, after restarting firefox.


End of hinukmattila's quote

What exact version of WindowBlinds were you using?

Reply #12 Top

WindowBlinds_10.8.4-sd-setup was the filename of the installer that i used, and also i'm using the newest windows 10 pro 2004 with the latest updates.