How to Stop Unresponsive Script Errors

Written by michael batton kaput
  • Share
  • Tweet
  • Share
  • Email

While there are a multitude of websites that you can access online using only your Internet browser, they are not all created equal. Some websites may not be coded correctly or may interact negatively with your Web browser settings. That can lead to problems, namely script errors. Script errors indicating that a script on the page is unresponsive can stop your Web surfing in its tracks and force you to stop necessary scripts on web pages. However, you can address unresponsive script errors by tweaking your browser settings.

Skill level:
Moderately Easy

Other People Are Reading


    Fix Script Errors in Internet Explorer

  1. 1

    Launch Internet Explorer and click "Tools."

  2. 2

    Click on "Internet Options."

  3. 3

    Click on the tab marked "Advanced."

  4. 4

    Click "Disable Script Debugging" if you use Internet Explorer version 6 or earlier. If you're using version 7 or later, uncheck the box next to the option labelled "Display a Notification About Every Script Error."

  5. 5

    Click on the tab marked "Security."

  6. 6

    Click "Default Level," then click "OK." Click on the tab marked "General" when finished.

  7. 7

    Click "Settings" next to the heading labelled "Temporary Internet Files." Click "Delete Files." Repeat the process for the "Delete Cookies" and "Clear History" headings. Click "OK" when finished.

    Fix Script Errors in Firefox

  1. 1

    Launch Firefox and click inside the Web address bar at the top of the screen.

  2. 2

    Type "about:config" and press "Enter."

  3. 3

    Click on the entry marked "dot.max_script_run_time."

  4. 4

    Type a number bigger than five in the box.

  5. 5

    Click "OK."

Don't Miss

  • All types
  • Articles
  • Slideshows
  • Videos
  • Most relevant
  • Most popular
  • Most recent

No articles available

No slideshows available

No videos available

By using the site, you consent to the use of cookies. For more information, please see our Cookie policy.