google-chrome-devtools

I'm using the Closure compiler to create a Chrome extension and I'd like to get source maps to work for debugging. I can get source maps to work just fine by pointing the browser directly to a page in my source tree with the special sourceMappingURL added to the end of the compiled javascript file (everything is in a single directory): debugger;document.getElementById("hello").innerHTML="Hello, world!"; //@ sourceMappingURL=background-compiled.map But when I access the same script as an extension, I can only see the compiled javascript and not the original source. I do have the Chrome debugger

The Chrome Network Tab in the Web Developer Tools shows that a bunch of my AJAX requests are taking 16027.8 days to complete. This is... not how long they are taking. I can replicate this on multiple machines, and in both development and production environments. This happens for all Dojo AJAX requests that are happening onload . It doesn't happen for other webapp or 3rd party requests (like signin AJAX or facebook). What is going on? Is our server somehow screwing this up? Is it a bug in chrome dev tools (it almost certainly is, right?), and if so, is there anything that can be done about it?

The problem is not that my console.log is not printed in the console. The problem is that the console is initially blank. I need to switch the tabs back and forth to get it working. Steps to reproduce: 1. Open Google chrome 2. Open some page 3. Open the console with Ctrl+Shift+I or F12 I even reinstall the browser (I kept the settings, because I can't afford to delete everything). Of course I removed all the extensions and disabled all the plugins. Still the same thing. Is there any application cache which I could delete to fix the problem. Here is a screenshot: P.S. The error which you see is

So in my javascript I'm making an ajax call to a service on my website. Whoops, something fails. No problem. Here's what I'd do in Firefox: Open the firebug console Find the failed Ajax call and click the + sign to see more info. The response tab has the raw HTML. Who wants to read all that? I click the HTML tab. Ah, the nicely formatted HTML returned by Django shows my divide by zero error. Now here's what I currently do in Chrome: Ctrl+Shift+J to open the Developer Tools Go to Resources Scroll down to the Ajax call and click Once again, I see raw HTML. Still don't want to read all that, but

I use Selenium and Chrome driver and also enabled performance logging to provide better visibility to problems during the test. Performance log seems to be a json array that includes chrome's DevTool protocol messages. Is there any tool existent that allows me to visualize this log like in Chrome's dev tools tab. Below is sample entry from the log: { "message": { "method": "Network.requestWillBeSent", "params": { "documentURL": "https://******/", "frameId": "15976.2", "initiator": { "type": "other" }, "loaderId": "15976.3", "request": { "headers": { "Accept": "text/html,application/xhtml+xml

I am trying to determine the rules for generating class names in javascript. I pasted this script into Chrome dev tools console: var obj = { Constr : function() { } }; var obj2 = obj; console.log(new obj.Constr()); console.log(new obj2.Constr()); obj2.Constr2 = function() { }; console.log(new obj.Constr2()); console.log(new obj2.Constr2()); And here are the results in the console: obj.Constr obj.Constr obj2.Constr2 obj2.Constr2 It seems that the name of the class is determined by the variable that the constructor function was originally assigned to. I am looking for the precise rules that CDT

I want to break when the class attribute is changed by a script. I tried it with "Break on: attribute modifications" but it doesn't break. Workaround The following code will only work if your browser supports MutationObserver . Open developer tools using F12 and execute the following code in the console: var Spy = /** @class */ (function () { function Spy() { } Spy.observe = function (targetNode) { Spy.observer.observe(targetNode, Spy.config); }; Spy.disconnect = function () { Spy.observer.disconnect(); }; Spy["break"] = function () { debugger; }; Spy.config = { attributes: true, childList: