{"id":1577,"date":"2012-06-04T09:01:56","date_gmt":"2012-06-04T16:01:56","guid":{"rendered":"http:\/\/juixe.com\/techknow\/?p=1577"},"modified":"2012-06-07T12:49:51","modified_gmt":"2012-06-07T19:49:51","slug":"javascript-debugging-console","status":"publish","type":"post","link":"http:\/\/juixe.com\/techknow\/index.php\/2012\/06\/04\/javascript-debugging-console\/","title":{"rendered":"JavaScript Debugging With The console Object"},"content":{"rendered":"

In the early days of JavaScript there were few options for debugging large web applications. You could have used the multiple alert notifications or possibly even calling document.write to write messages into the document. Firebug changed web developers lives, and I think how we view JavaScript, by making it incredibly easy to debug HTML, CSS, and JavaScript. Since Firebug, most current versions of web browsers include powerful debugging tools. In addition to the debugging tools browsers have made available a JavaScript console object<\/strong> to help write debug statements. With console, there is no need to pop up alerts to inspect the state of an object. To write a log message intended for the console, just write the following JavaScript statement in the right place.<\/p>\n

\r\nconsole.log("This is a log message");\r\nconsole.log("Message one", "Message two", "Message three");\r\n<\/pre>\n
To open the console, you can find it in Safari by looking for the the Web Inspector, in Chrome it’s called Developer Tools, and in Firefox you’ll find it under the Tools menu as Web Console.<\/p>\n
The console object has a lot of useful debugging messages for errors with different severity, such as log, debug, info, warn, and error.<\/p>\n
\r\nconsole.info("I'm here.");\r\nconsole.warn("Do I smell smoke?");\r\nconsole.error("The roof, the roof, the roof is on fire.");\r\n<\/pre>\n
In addition to logging String messages, you can log whole JavaScript objects.  It may be useful to inspect a complete object and it’s state.   To write out the state of an object to the console use the dir method as in the following example.<\/p>\n
\r\nconsole.dir({fname:"Bill", lname:"Gates"});\r\nconsole.dir(document.getElementById('SomeElementId'));\r\n<\/pre>\n
In Chrome and Safari, you can also use dirxml to display the a HTML element object in the console as HTML.  In my version of Firefox, this method did not work.<\/p>\n
\r\nconsole.dirxml(document.getElementById('SomeElementId'));\r\n<\/pre>\n
You can also group related log messages, no matter their severity.  To group console messages surround them with a group and groupEnd.  You can even nest groups inside of groups.<\/p>\n
\r\nconsole.group("Server update");\r\nconsole.log("calling server...");\r\n\/\/ ... any number of console log messages.\r\nconsole.groupEnd();\r\n<\/pre>\n
You can also test the performance of your JavaScript code with time and timeEnd.  Both of these methods accept a String label and it needs it needs to be the same value for both methods.<\/p>\n
\r\nconsole.time("Process Data");\r\n\/\/ ... some time consuming code\r\nconsole.timeEnd("Process Data");\r\n<\/pre>\n
When the timeEnd method is executed it will generate a message in the log console with the amount of time it took to run the code between the time and timeEnd method.<\/p>\n
\"Chrome<\/span><\/span><\/span><\/span><\/span>
Chrome Developer Tools Web Console<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"
In the early days of JavaScript there were few options for debugging large web applications. You could have used the multiple alert notifications or possibly even calling document.write to write messages into the document. Firebug changed web developers lives, and I think how we view JavaScript, by making it incredibly easy to debug HTML, CSS, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","footnotes":""},"categories":[13,16,3,4],"tags":[699,137,46,702,102,703,333,700,701,800],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p902K-pr","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"http:\/\/juixe.com\/techknow\/index.php\/wp-json\/wp\/v2\/posts\/1577"}],"collection":[{"href":"http:\/\/juixe.com\/techknow\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/juixe.com\/techknow\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/juixe.com\/techknow\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/juixe.com\/techknow\/index.php\/wp-json\/wp\/v2\/comments?post=1577"}],"version-history":[{"count":5,"href":"http:\/\/juixe.com\/techknow\/index.php\/wp-json\/wp\/v2\/posts\/1577\/revisions"}],"predecessor-version":[{"id":1579,"href":"http:\/\/juixe.com\/techknow\/index.php\/wp-json\/wp\/v2\/posts\/1577\/revisions\/1579"}],"wp:attachment":[{"href":"http:\/\/juixe.com\/techknow\/index.php\/wp-json\/wp\/v2\/media?parent=1577"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/juixe.com\/techknow\/index.php\/wp-json\/wp\/v2\/categories?post=1577"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/juixe.com\/techknow\/index.php\/wp-json\/wp\/v2\/tags?post=1577"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}