We can see the offending code highlighted - We're calling the loadImages function with bad parameters. Let's click on line 32 which contains the call to getType: The line number is now highlighted to indicate it has a breakpoint. Internet Explorer Bear in mind, IE behaves vastly differently from other browsers when it comes to JS errors, and reports on them in disparate ways. The error may be generated when the page loads. his comment is here
Open Internet Explorer. Please provide us a little information as to the error message, steps you're taking to get to the error, and any version information. share|improve this answer answered Aug 29 '10 at 16:09 Eli Grey 23.1k125283 calling console.log() can dump things in console. We can see that the iteration of the forEach is currently in the div element.
What can I do about a rock climbing ban? Forgot your password? The Call Stack shows us the "parents" of this function call.
Internet Explorer Bear in mind, IE behaves vastly differently from other browsers when it comes to JS errors, and reports on them in disparate ways.
Open wp-config.php and add the following line before "That's all, stop editing! The error may be generated when the page loads. We can also find more variable information on the right, under "Scope". Open the Console Go to the screen where you are experiencing the error.
Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the Issue is fixed - turn off script debugging and report the issue on the support forum, telling the volunteers that you turned on script debugging and it solved the problem. The first thing we want to do is to make sure we have "Pause on exceptions" enabled, which is the button on the right with the pause icon in it By We are happy to help, but will need some additional information.
A tearful farewell How could a smaller country successfully take control of a much larger country? Or click F12 Click on the Console tab. 2. But just like surgeons have scalpels, we have better tools available for us too: Namely, debuggers. Note: the line numbers in the script debugger are different than in the fiddle.
We have two ways to set a breakpoint: We can set a breakpoint using a debugger; statement We can set a breakpoint from the script debugger Let's start by using the But have a look at IE Developer Toolbar. The console will provide you with the error type, the location of the error and the line number The image above shows the error to be in jquery.js on line 2. If you don't see any errors try reloading the page.
If you do not have Tools at the top you can use the following shortcut: Ctrl + Shift + J Visit the page with the error.