I saved the UserChrome.css file you linked into my C:\Program Files\Mozilla Firefox\chrome directory, opened it and pasted the code into the bottom of all the content and rebooted Firefox.
Didn't work.
Just in case, I copied the file into C:\Program Files\Mozilla Firefox\defaults\profile\chrome as well. Still no buttons in the QUICK FIND bar.
I feel great n00bness within me. I MUST be putting it in the wrong place.
Make sure you name it userChrome.css- note the lowercase u. Also, it needs to be in the chrome folder of your profile, not the program folder. The same location as userChrome.js.
2. The linked UserChrome.css from a few posts back was filled with all sorts of code. Pasting the QUICK FIND code at the end of it never worked. But pasting the code into a blank Notepad file and saving it as userChrome.css worked perfectly. Hurrah!
Now for sleep. Ah, sweet sleep: Half my life well spent.
You'll have to wait at least a few days until I'll have time to look for a work-around. Should anybody want to step in for me, please be my guest!
logan wrote:it sounds like this will be coming to 2.0 as well
They're still discussing alternatives for the branch. First comes checking AMO for further potentially affected extensions (see bug 423732) and shipping Firefox 3.0 Beta 5 to a larger audience.
I saw mention of Components.utils.import(), but didn't spend any time on that. How about if you register a chrome directory and then load chrome://dir/content/userChrome.js? Would change the location of the file though.
Minefield users: Temporary work-around: userChrome.js 0.8.0+. This version will copy your script(s) to a cache from which they are loaded without causing the above mentioned issue on current Trunk builds. The only thing which won't work is the loading of further subscripts (through e.g. my Sub-Script/XUL Loader snippet).
For convenience, this version offers one method available from JavaScript anywhere:
(where filename is a path relative to your profile's chrome directory, e.g. <code>"mousegestures.uc.js"</code> or <code>aFile.leafName</code>). This will load your scripts through the same cache as userChrome.js itself. Note: Don't rely on this, if you don't have to!
mozillaZine is an independent Mozilla community and advocacy site. We're not affiliated or endorsed by the Mozilla Corporation but we love them just the same.