4 ms·
I agree that Chrome's dev tools are faster and crash less. I also find them more visually appealing. I wouldn't say they are better than Firebug, though... th
by photon_off 15y ago
I agree that Chrome's dev tools are faster and crash less. I also find them more visually appealing. I wouldn't say they are better than Firebug, though... there are a few kinks they need to work out.
One of them is console.log():
(function(){
var obj = {};
console.log(obj);
obj.new_value = "hello";
console.log(obj);
})();
In Chrome, this logs an object {new_value: "hello"} twice, as opposed to the expected: an empty object, and then the aforementioned object.
More details here: http://techblog.appnexus.com/2011/webkit-chrome-safari-console-log-bug/ http://techblog.appnexus.com/2011/webkit-chrome-safari-conso...
It's not something I encounter often, but when I do, it's really obnoxious to have to work around it. I mean, it's console.log() ffs.
- masklinn 15y agoYeah that one's a complete pain in the ass, it makes debugging much harder in mutation loops as you always get the wrong value displayed in the console and then smash your head in the desk as a test which should be hit is not.