Firefox Version 8.0

All replies

• 

  

  1

  Sign in to vote

  Hi dbasnett !

  The issue is not related to the browser;

  You can see this has been discussed ealier in below thread;

  http://social.microsoft.com/Forums/en-US/reportabug/thread/a5fc84e4-4817-4010-a287-db1bddaf9ab5/#2fb009ab-e7a2-416c-9b5a-58c60b104cdd

  And its a known issue according to Bent.

  Thanks, Hasham

  • Proposed as answer by Richard MuellerMVP, Moderator Sunday, November 13, 2011 3:19 AM
  • Marked as answer by Ed Price - MSFTMicrosoft employee, Owner Wednesday, November 30, 2011 8:39 AM

  Sunday, November 13, 2011 12:33 AM

  Reply

  |

  Quote

  Moderator
• 

  

  0

  Sign in to vote

  I don't recall having this problem before the update.  It was slow at times... 

   

  I get this in a dialog box now:

   

  A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.
  
  Script: http://code.jquery.com/jquery-1.6.1.min.js:16

   

  If I click continue, sometimes more than once, the page eventually loads.

   

  ---

  Serial Port      Random      Microsoft® Community Contributor 2011
  

  • Edited by dbasnett Sunday, November 13, 2011 12:09 PM

  Sunday, November 13, 2011 12:08 PM

  Reply

  |

  Quote
• 

  

  0

  Sign in to vote

  It happens, regardless of FF version.

  One thing to be a guard for is if any used domains are blocked in NoScript.

  Monday, November 14, 2011 12:36 PM

  Reply

  |

  Quote
• 

  

  0

  Sign in to vote

  It happens, regardless of FF version.

  One thing to be a guard for is if any used domains are blocked in NoScript.

  It did not happen before upgrade to 8.0.  It was slow at times, but I never saw the script error dialog.  And as I said, clicking continue seems to work.
  

  ---

  Serial Port      Random      Microsoft® Community Contributor 2011

  Monday, November 14, 2011 1:15 PM

  Reply

  |

  Quote
• 

  

  1

  Sign in to vote

  It happens to me sporadically. I am using 3.6.24, and it happened in earlier versions as well.
  

  Monday, November 14, 2011 1:45 PM

  Reply

  |

  Quote