I finally figured out how to get Firefox to do NTLM, which means I don't have to deal with the authentication dialogs, thereby reducing my dependence on IE to one and only one application (Oddpost).
It's not at all obvious how to make it work, and it took me a few tries. You have to go to your Firefox address bar and type about:config. This will bring up the internal config editor, which allows you to set all kinds of properties that influence Firefox's behavior. Look for the key called network.automatic-ntlm-auth.trusted-uris. Set that key's value to a comma separated list of servers you want NTLM auth for. So if your internal SharePoint sites are on servers called Larry and Mo, use "larry,mo". You can also add the same value to the key network.negotiate-auth.trusted-uris. It's unclear to me if that second one is required, but I set it, and everything works. Now SharePoint works like a champ, and authenticates automatically.
1 Customize the Interface
2 Add Some Action
3 Take Stock
Update the two Contents.rdf files by replacing all the occurrences of wikipedialookup with the name of your extension. Make sure that the Contents.rdf file in the content folder correctly points to the filename of your XUL file. When you're done, rename the ZIP archive (the one containing the skin and content folders) with a .jar extension.
4 Update the Install Script
There are six lines to update in the Install.rdf file: the name of your extension, the version number, the creator (you), a brief description, the name of the .jar file, and a unique ID that differentiates your extension from all others. Update the Install.js file in the same way so your extension will also install on SeaMonkey, Mozilla Suite, and Netscape.
5 Put It Back Together
With all the files updated, rename the main ZIP file with an .xpi extension again. Make sure that the directory structure exactly matches the example XPI. To install your extension, drag and drop your XPI file onto an open Firefox window, and then restart Firefox.
6 Check Your Work
Test your extension on a real Web site. If you get an error, or if something doesn't work, retrace your steps and see if you missed anything. If you want to share your extension with others, or to get help or see other examples, visit developer.mozilla.org/en/docs/Extensions.
This is very useful for developers who are always using the 'view source' function. This tweak allows you to view the source code in an external editor.
There are two configuration need to be made: Config name: view_source.editor.external Default: False Modified value: True ( enable view source using external text editor) Config name: view_source.editor.path Default: blank Modified value: insert the file path to your editor here.
onfig name: network.http.pipelining Default: False Modified value: True Multiple requests send before any responses received http://kb.mozillazine.org/Network.http.pipelining Config name: network.http.proxy.pipelining Default: False Modified value: True Same as above but with proxy Config name: network.http.pipelining.maxrequests Default: 4 Modified value: any value higher than 4, but not more than 8 Max # of requests to pipeline when pipelining is enabled Config name: network.http.max-connections Default: 30 Modified value: 96 Max # of simultaneous http connections that can be issued. Rest are queued. Config name: network.http.max-connections-per-server Default: 15 Modified value: 32 Max # of simultaneous http connections per server. Rest are queued.
Filter: browser.urlbar.formatting.enabled (for 7+) Filter: browser.urlbar.trimURLs (for 9+) in lower panel, double-click that item to toggle value to false