Just wanted to give an update on the issue my client was having with Firefox. I finally was able to schedule a WebEx demo with the client.
After some debugging, we discovered that the browser was crashing on the window.close() method (and any variation of it, i.e. self.close(), etc.) Anyway, booting in to Firefox's safe mode made everything work correctly. This led me back to an extension being the problem. My original hunch proved correct, in that it was the Tabbrowser Extensions v2.1.2006031301 that was the culprit. While the client had disabled the extension, it seems this wasn't enough. Only after removing the extension did the problem go away. I believe this might be because Tabbrowser Extensions has a custom config file that gets loaded--even when the extension is disabled. Anyway, I made the mistake of not having the customer go into safe mode from the start (I had actually forgotten about the option.) So, in the future if you have a client having problems with Firefox and you know it's working for you, make sure the client boots into safe mode as the first step to see if they still experience the problem. http://kb.mozillazine.org/Safe_mode "C:\Program Files\Mozilla Firefox\firefox.exe" -safe-mode Extensions are a wonderful thing, but they can also cause instability. -Dan ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/cf_lists/message.cfm/forumid:4/messageid:245667 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
