« Troops Ask John Kerry For Help | Main | My election day prediction »
Ever since I installed Mozilla Firefox 2.0 I have noticed that certain file extensions that I used to be able to "Open" by clicking now pop up this new dialog box that doesn't show the open option at all, and only allows FlashGot. It took me a while to realize that there was a "Save" button that would allow me to save the file, and open it from the download manager. Why should I have to go through the extra step.
I did a bit of googling, and found this flame war that erupted in July while Firefox 2.0 was still in Beta, which lead me to bug #315536 and yet another flame war.
It appears as if the intent was to "protect" people from accidentally configuring Firefox to always open executables without prompting. In my opinion, they threw the baby out with the bath water, and now any mime-type that isn't explicitly configured in Firefox gets the new screwy dialog:

This annoyed the hell out of me, so I decided to try a suggestion from that first flame war. I found the nsHelperAppDlg.js file in C:\Program Files\Mozilla Firefox\components and changed:
if (shouldntRememberChoice && noDefaultApp) {
To:
if (shouldntRememberChoice && noDefaultApp && false) {
After a quick restart of Firefox, the dialog changed to:

This may get overwritten if I upgrade/re-install Firefox, but I can deal with that. This is a simple enough change that just about anyone should be able to do it. It's always a good idea to make a backup copy of the file before you make the change though. Enjoy!
Update: If you are having trouble with this workaround after updating to Firefox 2.0.0.2, read this update.
TrackBack URL for this entry:
http://www.jmarler.com/movabletype/mt-tb.cgi/222
Comments
thx, helped me out!
Posted by: felix | January 12, 2007 11:58 AM
man I have been looking for this fix for awhile --- I found "OpenDownload" extension not too long ago, but this is great as it accomplishes exactly the same thing without an extension...
Thank you very much for sharing the procedure to modify this behavior....
Posted by: G MoNeY | February 15, 2007 2:49 PM
Well, this was helpful, but since updating to 2.0.2 this morning, I can't figure out how to get this back. There is no noDefaultApp string now, so I'm not sure what to change. Any chance for additional help?
Posted by: RagManX | February 24, 2007 2:24 PM
RagManX -> I see that ...
For some odd reason, my Firefox's behavior hasn't changed.
I'm looking into it ... I'll post an update as soon as I figure it out.
Posted by: DJFelix | February 24, 2007 3:45 PM