Firefox Usage

Hardware Acceleration

• For nVidia cards, it is necessary to get VAAPI working first (in addition to setting the hwaccel USE flag). Check this page for more information.
• Note that unfortunately, Firefox on Linux is extremely slow compared to the same computer on Windows. This is true for the 117 version, with a nVidia card and binary drivers. The situation may be better with an AMD card, but currently, Firefox is really sluggish (especially for web games and anything related to the display/drawing aspects).

Extensions

• Firebug: Unfortunately the key shortcuts cannot be customized it seems. It is an excellent extensions when debugging JavaScript code.

• Web Developer Toolbar: You can configure this add-on to open a page's source in a tab instead of a window, very useful! Plus you can configure it to open the pages in your favorite editor, but it does not accept command-line argument so you must write a wrapper. You can change the keys shortcuts.

• LiveHTTPHeaders: Extremely useful when you need to analyze what's happening between the browser and the server.

• ColorZilla: Includes an excellent color picker for web design. Unfortunately does not work on 64-bit platforms. Update: does not seem to work anymore even on 32-bit, and latest version (beta 2) prevents Firebug from working.

• HTML Validator: Can be used to see quickly if your pages are W3C compliant. Currently renders Firefox 2.0.0.11 completely unusable.

• Total Validator: Another tool to check page compliance, seems to work better.

• CacheToggle: turns the cache on and off, very useful.

• Rubyfox: Nice theme to relook Firefox.

Web Development

• A really annoying bug seems to be that Firebug / Firefox error console is not able to catch errors present in Prototype Ajax callbacks. Opera has the same problems. When using normal hand-coded Ajax calls, errors are caught but there still seems to be problems. See this bug.

• If Firebug starts behaving strangely (not logging JS errors in the console). reinstalling it after uninstalling it may help.
• UPDATE: a much better way is to look into prefs.js (in the profile directory) and see if the FB keys seem normal. In my case there was a key set to false which was preventing the logging of JS errors in the console.

• If you have a strange "cannot access optimized closure" message in Firebug (with Firefox 3.5), then you are hitting something else in fact (like accessing an undefined variable). Try to run the script in another browser like Opera to find the real cause.