How Do I Diagnose JavaScript Errors on My Site?

Websites use several different Website coding languages to work. All websites use HTML, CSS, and JavaScript to render the webpage to the visitor.

When the website is loading but the website is not displaying correctly, this is usually due to a coding error on the site. Usually this is caused by JavaScript or CSS errors. This article will focus on diagnosing JavaScript coding errors.

How do I know its a JavaScript problem?

JavaScript is used to make different behaviors happen on your site. These behaviors are all done through the Visitor of the sites browser. Examples of this are Image Slide Shows, Pop Up boxes, Menus, and more. When your website loads, but the behaviors on your site stopped working, this is usually because of the JavaScript code not working.

What happens when your JavaScript fails?

If you have JavaScript’s on your site that are not working you can diagnose them by using your browsers “Error Console“. Each browser has a built in “Error Console” for diagnosing scripting errors on your site. Below will show you how to check the “Error Console” in FireFox, Internet Explorer, Chrome, Opera, and Safari.

Diagnosing a JavaScript error

Simple JavaScript pou up Error Console

In order to explain how to diagnose a JavaScript error, we will use the simple “pop up” script below (Snapshot to the right shows what it does):


This script simply creates a pop up box that says “I am an alert box!“. We will break the script so that is causes an error by removing one of the quotes like the following.

Broken code for example Error Console

When the website is ran, the code will break where the quote is missing. The snapshot to the right shows the code that’s broken, and where the lines are in the code.

In this case Line 33 is broken. The methods below will show you how to find the lines of broken code through your browser.

Javascript console for FireFox

Using the code example from the “Diagnosing a JavaScript error” section above, We will find the JavaScript error using Firefox.

  1. Open FireFox.
  2. Fire fox Error Console tools

    Go to Tools > Web Developer > Error Console. If you do not have Tools at the top you can use the following shortcut:

    Ctrl + Shift + J


  3. FireFox Error Console window

    Visit the page with the error. In this case you will see the error on Line 33 in the FireFox Error Console. See image to the right.

Javascript console for Internet Explorer

Keep in mind we are using the code example from the “Diagnosing a JavaScript error” section at the beginning of this article. Below is how to use the Error Console in Internet Explorer.

  1. Open Internet Explorer.
  2. Press the function key on your keyboard, F12.
  3. Internet Explorer Error Console

    Visit your webpage with the error. You will see the error with the line number of where the error occurs in the document in the bottom Error Console window. The snapshot to the right shows the error on line 33.

Javascript console for Chrome

From the “Diagnosing a JavaScript error” section example towards the top, we will find the JavaScript error on a webpage in Google Chrome.

  1. Open Google Chrome.
  2. Click the “Customize and Control Google Chrome” button at the top right side.
  3. Chrome tools Error Console

    From the drop menu, go to Tools > JavaScript console. Or you can press:

    Ctrl + Shift + J


  4. Chrome Error Console window

    Visit the site with the error. In the Error Console window you will see the error show on line 33. See image to the right.

Javascript console for Opera

Continuing to diagnose the error from “Diagnosing a JavaScript error” section, we will find the JavaScript error on a webpage in Opera.

  1. Open Opera.
  2. Click the Opera button towards the top right.
  3. Opera page developer Error Console

    Navigate to Page > Developer Tools > Error Console. Or you can press the following keyboard keys:

    Ctrl + Shift + O



  4. Opera Error Console window

    The Error Console will pop up. You can move the window to the side while you visit your site. You will see the errors list when you visit the site with the broken code. The image to the right shows the error on line 33.

Javascript console for Safari

Continuing the previous example error from “Diagnosing a JavaScript error” section, We will look at the Error Console in Safari.

  1. Open up your Safari browser.
  2. Click the “Display a menu of general Safari settings” button towards the top right that looks like a gear.
  3. Safari Preferences Error Console

    Click Preferences.

  4. Safari Show Develop menu Error Console

    On the Advanced tab, make sure you have the “Show Develop menu in menu bar” box checked.

  5. Show the Error Console in Safari

    Display a menu for the current page” icon towards the top right that looks like a paper with a bent corner.

    Go to Develop > Show Error Console. Or you can press:

    Ctrl + Alt + C


     


  6. Safari Error Console window

    Visit your webpage that is broken and check the Error Console at the bottom. The errors will list when you refresh your browser. In this case you can see the error on line 33 in the snapshot to the right.

Thoughts on “How Do I Diagnose JavaScript Errors on My Site?

    • Unfortunately if safari is not showing you all the information your best bet would be to see if you can replicate the error in Chrome or Firefox as they have much more robust developer tools and troubleshoot from there. If you cannot see the error in other browsers i would recommend putting in a bug report with Apple to see if they can see why the browser is not giving you the information it should.

    • Hello Ashraf,

      Javascript is mostly processed on the browser side. Browsers now have developer tools built into them so you can work on scripts, etc. Each one is different, but you can usually access the tools by right clicking the page and then use the “Inspect Element” option. A window will appear at the bottom giving you access to several tools to help you with your site scripts.

      Kindest Regards,
      Scott M

    • Hello. I know this is an old thread, but are the moderators (John-Paul and Ann) still available to assist? I’ve similar issue with JScript error: Input_0:689: ERROR – Object literal contains illegal duplicate key “getSelected”, disallowed in strict mode },getSelected:function(){return this.selectedRows;},serialize:function(){var a=this.previous.apply(this,arguments)||{};if(this.options.selectable){a.selectedRows=this.selectedRows.map(function(b){return Array.indexOf(this.body.rows,b); ^^^^^^^^^^^ Input_0:696: ERROR – Object literal contains illegal duplicate key “getSelected”, disallowed in strict mode c++){if(this.options.selectHiddenRows||e[c].isDisplayed()){this[g](e[c],true);}}return this;},deselectRange:function(b,a){this.selectRange(b,a,true);},getSelected:function(){return this.selectedRows; ^^^^^^^^^^^

    • In Googling around for this error, I discovered that it affects some Joomla users using an infinite scroll module. I advise checking your Joomla version and perhaps checking for any recent module installations. Also, I could not reproduce the error in Google chrome. Your domain was redacted for privacy reasons.

    • Hello Ashraf,

      we need a little more information in regards to the errors before we can attempt to resolve them. Please provide us a little information as to the error message, steps you’re taking to get to the error, and any version information.

      If you have any further questions, please let us know.

      Kindest regards,
      Arnel C.

  • how would i know the exact error in javascript like error shown in c c++ etc in those programming language we get the exact line no. where the error is what is missing finally my question is why javascript is not showing exact error, exact line number details of error on console, sometime it shows error in jquery.js etc its tooo frustrating to debug the js can anybody help to resolve the js issues…thanks

    • Hello Sarthak,

      I am not sure if we are following you completely, can you provide us the code that is providing an error but not specifics so we may attempt to solve the issue.

      Kindest Regards,
      TJ Edens

    • Hello Bally,

      Thank you for your question. We are happy to help, but will need some additional information.

      What is the full error you are getting?

      Can you provide a link to the error, or domain name?

      What are you trying to accomplish?

      Thank you,
      John-Paul

Leave a Reply