After successfully testing WindowBlinds in a VirtualMachine I was ready to try it on my actual system and got a small shock. I heavily modified my UserChrome.css of Firefox and found that WindowBlinds replaces it without warning or notice leaving me shocked why my Firefox looked stock suddenly. Now it thankfully makes a backup and I also had my own backup but I would atleast appreciate a warning so the user knows what going on.
Something like:
"To theme the window controls of Firefox WindowBlinds has a custom UserChrome.css file for it. If you already made modifications to it you might not need this file. Do you want to replace it?
YES/NO"
Likewise WindowBlinds also replaced ThemeInit.dll making me wonder why I couldn't apply .msstyles themes anymore after uninstalling WB to find the root-cause of the issues. I'm aware that WindowBlinds needs to do these things to function and keep a consistent theming experience but please add warnings for these things. While regular users won't know anything changed power users who already made changes will be left confused.
