I had two emails into SD themselves but i never got a response. So I was just trying. At least I have it so it does not overwrite any longer. I have a feeling not many in that circle even realize WB writes over those files. I understand why they did it before, but useChrome.css is now the ONLY way to make deeper changes to FF now that web extensions is active. I use most browsers, At .least the top 4 because the tools and toys i write for my customers have to work on those. I am not&nbs
danamw
Wtf is that? Windowblinds doesn't write to other programs to skin it and as i stated before you HAVE TO USE THAT FILE TO MAKE CHANGES TO FF 57+ so why would i want a program to over write it every time it runs. If that is your level of help here sorry i asked. Well more like sorry you answered. I guess you don't understand that windowblinds is overwriting user files, that is files people use and should not be overwritten. Now for people that have actual need of facts the problem
I want firefox skinned of course and anyway it does not prevent the overwrite. It seems this behavior is hard coded into Windowblinds.
Windowblinds writes to the firefox user profile folder every time it is run. It overwrites the userChrome.css with the file ff.css from the windowblinds folder, I want to skin Firefox but i don't want some program writing to my user files without my permission. This is even MORE important in Firefox 57 which makes it so the ONLY way to change things for a user is now userChrome.css in the profile/chrome folder. The extensions can no longer write to another extension. My questi
I wanted to mention some issues i had with the skin "Scarlet Updated Sep 13, 2017 by LightStar". Copy of my post to lightstar "I really like this skin but i also had trouble with it and the title bar area. It caused firefox dev ed. to go transparent and for the "control-box" (the exit,min and restore) button to stop working and it was NOT a corrupt file or driver this is a brand new dell w