I have a very strange problem with Firefox which has me totally stumped, and it is driving me nuts.
Whenever I try to do ANYTHING in Firefox which requires the use of the Common File Dialog, the file dialog does not show. The issue is not isolated to saving a file (although, that is where I first noticed it). It is definitely an issue with trying to display the common File dialog itself - be it for saving a file from a link, or File -> Save Page As, or File -> Open File, or Bookmarks -> Show All Bookmarks -> Import and Backup (to/from HTML), Export, etc., etc. No matter what type of file operation it is, the file dialog never appears.
Here are the things I have already tried (not necessarily in this order):
Run Firefox in Safe Mode
Create a New Firefox Profile
New Firefox Theme (then revert to Default)
Although I am using Firefox v28.0, I also tried regressing to v27.0.1, and still saw the same (mis)behaviour.
I am running Firefox in an admin level (Windows) account in this case - so, there shouldn't be any permission issues there.
As listed above, I have tried shutting down both the desktop firewall software (Agnitum Outpost Pro), and the anti-virus (Avast), and the problem still persists exactly as described. Obviously, I disconnected the system from the 'Net when I did that.
All other software that I have tried on the system interacts with the file dialog just fine ... so, I don't think it is anything central like some corruption associated with the file dialog itself. It really does seem to be isolated to Firefox.
I tried a few malware scans (even though I didn't really think that was it - there were no other systems), and they showed clean.
I've tried running Sysinternals ProcMon to get a better look at what is going on, but I haven't been able to hit on just the right combination of filters to reveal the actual problem (without it being buried in way too much "noise" [shrug]).
This is a very "interesting" one. I am a database admin by trade, and I was a programmer in a previous life - so, I consider myself to be relatively tech savvy (though I am not arrogant enough to consider myself an expert in everything). I have never run across anything else quite like this, and I am totally perplexed. Does anyone have any ideas how else I can troubleshoot this - or better yet, fix it?
PS - This is on a WinXP SP3 system. (Don't laugh - there's a 3rd party software compatibility issue driving that need, for the moment. In the next few months, I should be able to finally upgrade to a newer O/S.)
Edited by brantb, 21 April 2014 - 07:18 PM.