Re:Firebug lead developer now working on Web dev tools at Go...
by tlrobinson on Sunday July 17, 2011 @09:47PM
(#2774803)
Regarding #1, you can do multiline if you paste, or option-return.
Re:Firebug lead developer now working on Web dev tools at Go...
by chrisbroadfoot on Sunday July 17, 2011 @11:03PM
(#2774939)
Chrome can do #1 and #2.
Re:Firebug lead developer now working on Web dev tools at Go...
by masklinn on Monday July 18, 2011 @04:20AM
(#2775527)
2 only partially: it does not link to the DOM tab.
Re:Firebug lead developer now working on Web dev tools at Go...
by photon_off on Monday July 18, 2011 @12:53AM
(#2775156)
How do you do #2?
1. The console is a lot better. You aren't limited to the one line interpreter that Chrome provides.
2. Using console.log, and console.dir I get a colored DOM/JSON output. I can click the DOM element and it'll get me to the DOM/HTML tab. This is not available in Chrome. I can move the mouse over the DOM element and it'll be highlighted in the browser.
3. Add-ons: I use the jQuery and Cookies add-ons and they add a lot to the console. I can include jQuery with a click and it highlights the jQuery objects for me in the console. I can watch cookies changes from the console directly.
4. For the debugging tools, they are equal. For syntax coloring the JavaScript code, there is a Firebug add-on for that.