The resulting situation is that the File Save dialog _ keeps input focus_ (and still has some local functionality), butīoth "save" and "cancel" buttons are disabled, so the File Save dialog cannot be removed (closed) and one cannot When it ends up being unresponsive itself:ĭue to this, it can cause a hang-up of Firefox that can be amended only by killing and restarting the application.Ī concrete example is when the "extended running time of a script" is caused by (or triggered while) a File Save dialog is open: the unresponsive script warning dialog will then pop up logically _ behind_ the File Save dialog (at least in Mac OS X, panther (10.3) through leopard (10.5)). Unfortunately, the "unresponsive script error" is (still) fundamentally broken since it does not notice So far I’ve not had anymore unresponsive script warnings, so I guessed that fixed that problem! However some extensions may also cause similar problems. If you can’t find the string in the about:config page, create it by right-clicking anywhere and then choose New-> Integer and enter dom.max_script_run_time.
This is the maximum time a script can run before Firefox considers it 'unresponsive'. Change the number to something bigger like 20. This will narrow the options till only the dom.max_script_run_time option remains. In the 'Filter' box, type dom.max_script_run_time. Just type about:config in the address bar and you’ll get a page full of hidden configurations which you can tweak till your heart’s delight.
To fix it, you’ll need to access the hidden configuration page in Firefox.
JAVASCRIPT UNRESPONSIVE SCRIPT FIREFOX HOW TO
Curious about it, I dug around and managed to find out how to fix the problem. I found a fix that worked for me, maybe it will work for you too.Įver since I upgraded to Firefox 1.5, I’ve been getting some unresponsive script warnings on sites that employ heavy Javascript like Gmail or Bloglines. I was getting unresponsive script error problem after installing firefox 3.5 update.
0 kommentar(er)
