Hey!
Since the introduction of Firefox 3 or 4 (I don't quite remember) and the removal of the status bar I have liked to use the Add-on bar instead. In the newer versions of Firefox, however, that Add-on bar comes with a closing button, an X on the very left.
Unfortunately, there is no built-in option to disable that particular button. Right-clicking and "Customize ..." doesn't allow moving or removing that button either.
After searching the web for a while, I stumbled upon a Google Groups thread: https://groups.google.com/group/mozilla.support.firefox/browse_thread/thread/d4a77426b84fe2b0
In that thread, Chris Ilias gave a simple solution (thank you!):
- Go to your Firefox profile directory. For that, just enter about:support in your URL bar (or click on Firefox => Help => Troubleshooting) and click on the "Open Containing Folder" button next to "Profile Directory".
- Close Firefox. (So maybe it would be better to continue reading these instructions beforehand and/or copy them into a text editor. 🙂 )
- Enter the subfolder "chrome" in the profile directory.
- Open the file "userChrome.css". If it does not exist, copy "userChrome-example.css" and rename the copy to "userChrome.css".
If you are using Notepad, you won't be able to see line breaks / new lines. Therefore I recommend using a program that can interpret these kinds of line breaks, for example TextPad, Notepad++ or even WordPad, which comes with Windows itself.
- Add the following line to the file:
#addonbar-closebutton { display: none }
- That's it! Save the file, start up Firefox again and enjoy the Add-on bar without a closing button!
These instructions were written for Firefox 11, but they should stay viable for the next couple of versions as well.
I hope this was of any help to you.
Thanks for reading!
Like this:
Like Loading...
Hi there!
When I implemented AJAX today in a new script of mine and persuaded 😛 a couple of friends of mine to visit the page, I found that the Chrome users received error messages when trying to use the AJAX functions. However, they actually worked. The server received the AJAX request and processed it correctly, leaving me scratching my head.
Turns out that Chrome only received an empty AJAX response in responseText which caused the JavaScript function to throw out an error message. But why was it empty?
A couple of web searches later I realized that apparently not too many people had come across that problem. Luckily enough I found a post in a forum that pushed me in the right direction.
Chrome seems to be a little sensitive concerning headers in the AJAX responses. Because I hadn't given my server-side AJAX processing script the appropriate "Content-Type: text/plain" header, it didn't "accept" the response as text.
Why it has to be so picky, however, I cannot understand 🙂
If you have encountered that problem before, I hope I managed to help you out.
Certainly made me go a little crazy for a while there 😛
Like this:
Like Loading...