Or click F12 Click on the Console tab. 2. Then use your app for a bit or reload the page and then click the "Profile" button again. 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. However, it is hard to follow the logic sometimes when the code is in a single block. this contact form
It looks like the type value comes from the getType function, so we need to go into it and find out what goes wrong. You can play around with each of these options to get a better understanding. Search Search Ask the Community! We can patch over the symptom and pretend like the bug doesn't exist, but this just leads to messy code and tons of special-case fixes for things nobody really understands.
You can have a single condition, or by using logical statements, break on a more complex condition. Finding the problem The first step in finding the problem is looking at the error message. The watch variable list displays values whether you are debugging code or not. look at this web-site Getting started To get started, we can open up the Developer Tools either through the menu, by right clicking the page and choosing "Inspect Element", or by pressing F12 (or Cmd+Opt+i
Firebug's script file chooser sorts and organizes files into very clean list that will help you find any file in a snap. You can click any button to jump to the line where that function is paused, and look at the local variables inside that function. We can start searching for the root cause by looking in the Call Stack on the right. navigate here Below will show you how to check the "Error Console" in FireFox, Internet Explorer, Chrome, Opera, and Safari.
With Firebug, you'll never again wonder why your code is slow.