Internet Explorer 9 Error Console
Contents |
resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events Community Magazine Forums internet explorer console log Blogs Channel 9 Documentation APIs and reference Dev centers Samples Retired console.log ie10 content We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. internet explorer console commands How-tos and Samples (by IE version) Internet Explorer 11 Samples and Tutorials Using the F12 developer tools Using the F12 developer tools Console Console Console DOM Explorer
F12 Console Commands
Console Console error messages Debugger Network UI Responsiveness Profiler Memory Emulation Keyboard shortcuts TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Using the Console to view errors and debug Use the Console tool to view f12 console tricks errors and other messages, send debug output, inspect JavaScript objects and XML nodes, and to run JavaScript in the context of the selected window or frame. A window into your code The primary use for the Console tool is to communicate into and out of running webpages: In: You run JavaScript to view and change values in running webpages, add functions to running code, and run debug code on the fly. Out: Internet Explorer and JavaScript code deliver status, error, and debug messages to developers, including inspectable JavaScript objects and DOM Nodes. Sending info to the Console Selecting your execution target Messages Internet Explorer sends to the console Messages developers can send to the console from code Managing messages for readability Selecting your execution target New in Windows 8.1 Update, the Console has a Target drop-down menu just above the Console output pane. If the webpage you're viewing has an iframe element in it, select the iframe from the Target menu to run Console c
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the internet explorer 11 logging company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions
F12 Console Hacks
Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million
Internet Explorer Event Log
programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Does IE9 support console.log, and is it a real function? up vote 180 down vote favorite 63 In which circumstances https://msdn.microsoft.com/en-us/library/dn255006(v=vs.85).aspx is window.console.log defined in Internet Explorer 9? Even when window.console.log is defined, window.console.log.apply and window.console.log.call are undefined. Why is this? [Related question for IE8: What happened to console.log in IE8?.] javascript logging internet-explorer-9 share|improve this question asked Mar 29 '11 at 13:03 mloughran 5,52462020 3 Check out this great post about the intricacies of IE8-9 console object/function: whattheheadsaid.com/2011/04/… –Marc Climent Dec 30 '11 at 13:37 See also 'console' is undefined http://stackoverflow.com/questions/5472938/does-ie9-support-console-log-and-is-it-a-real-function error for internet explorer –Bergi Nov 10 '12 at 12:34 add a comment| 7 Answers 7 active oldest votes up vote 261 down vote accepted In Internet Explorer 9 (and 8), the console object is only exposed when the developer tools are opened for a particular tab. If you hide the developer tools window for that tab, the console object remains exposed for each page you navigate to. If you open a new tab, you must also open the developer tools for that tab in order for the console object to be exposed. The console object is not part of any standard and is an extension to the Document Object Model. Like other DOM objects, it is considered a host object and is not required to inherit from Object, nor its methods from Function, like native ECMAScript functions and objects do. This is the reason apply and call are undefined on those methods. In IE 9, most DOM objects were improved to inherit from native ECMAScript types. As the developer tools are considered an extension to IE (albeit, a built-in extension), they clearly didn't receive the same improvements as the rest of the DOM. For what it's worth, you can still use some Function.prototype methods on console methods with a little bind() magic: var log = Function.prototype.bind.call(console.log, co
fixing it, I used it as an excuse to let Jamie be the IE debugging master (he just loves this). But http://thisbythem.com/blog/whats-up-with-the-js-console-in-ie9/ last week we were in the final stages of QA on a project making heavy use of Backbone.js, and one of the last things remaining was a bug that was only appearing on IE9. This bug was breaking the core functionality of the app. We were crunching and Jamie was busy, so I needed to get that VMWare instance going ASAP and dig in. internet explorer I used to be really good at debugging IE because I did it all the time. I used to know all the things to check and all the various hacks and such that were needed. But I was out of practice and this bug was killing me. I was having a really hard time reproducing it. But I finally found the steps: Fire internet explorer console up a new IE9 session on BrowserStack (for some reason it only happened on BrowserStack for me). Login to the app. Boom. Bug. It took me a couple frustrating hours to get to this point, mind you. But once I was able to reproduce, I thought it was going to be smooth sailing to finding a fix. Not quite. If I did the above steps, but had the developer console open, no bug. So, sprinkling some console.log messages at various points in the execution path to find out when this was happening wasn’t possible, because the bug wasn’t happening. Eventually, I asked Jamie to pair up with me on it, and he wondered if we had any console.log calls lingering in the codebase that we had forgotten about. I wasn’t convinced that would be the issue. The fact that these console.log messages were working was what had tricked me into thinking IE9 fully supported console.log. That was where I went wrong. In IE9, window.console is defined only when the developer tools window has been opened Grrr. That’s right. I had forgotten about this. Until you open the developer t