3 ms·

I totally understand it's way easier to start from scratch. It's a little disappointing to hear that the Firebug team didn't want to play ball. It's not a big

by mmuro 14y ago

I totally understand it's way easier to start from scratch. It's a little disappointing to hear that the Firebug team didn't want to play ball. It's not a big deal and I can continue to use Firebug, but the UI decisions still baffle me. Safari and Chrome display the HTML (which 90% of the time is what I'm after to begin with anyways) upon inspection with the CSS on the side. Being able to turn these off would be fine by me, but don't make me opt in every single time. Also, having the Console and other browser inspections would really take it to the next level. Functionality notwithstanding, I really like the look and feel of it.

jlongster 14y ago
Please file bugs at bugzilla.mozilla.org! This kind of feedback is very beneficial. (Disclaimer: I don't work on the devtools, but I work at Mozilla) That's a small tweak and shouldn't diminish the overall awesomeness that is the rest of the devtools. I actually agree with you, but have found them extremely fast and usable overall.
bzbarsky 14y ago
"Didn't want to play ball" has negative connotations that I certainly didn't mean to imply with what I said. It was just the priorities and goals that were different (e.g. back when JJB was still working on Firebug as part of his job at IBM Research, his work on Firebug needed to have a "research" component, as I understand, which led to some differences in approach from a pure "create a product" tack).
dangoor 14y ago
Just to reiterate what bz said for emphasis: it wasn't a matter of Firebug "playing ball". The choice to build afresh was made based on the direction that they wanted to go at the time and our own assessment of how we could get something reliable into the product. Also, Firefox 13 (which enters beta this week) has a bunch of nice improvements including remembering whether the HTML and Style panels are open. http://hacks.mozilla.org/2012/03/firefox-aurora-13-developer-tools-updates/ http://hacks.mozilla.org/2012/03/firefox-aurora-13-developer... We're iterating at a decent pace on these tools, so keep watching. The JavaScript debugger is coming to Aurora soon and it's shaping up quite nicely. The work behind that is going to be a big win for both the new debugger UI in Firefox and ultimately for Firebug as well.

by mmuro 14y ago

jlongster 14y ago

Please file bugs at bugzilla.mozilla.org! This kind of feedback is very beneficial. (Disclaimer: I don't work on the devtools, but I work at Mozilla) That's a small tweak and shouldn't diminish the overall awesomeness that is the rest of the devtools. I actually agree with you, but have found them extremely fast and usable overall.

bzbarsky 14y ago

"Didn't want to play ball" has negative connotations that I certainly didn't mean to imply with what I said. It was just the priorities and goals that were different (e.g. back when JJB was still working on Firebug as part of his job at IBM Research, his work on Firebug needed to have a "research" component, as I understand, which led to some differences in approach from a pure "create a product" tack).

dangoor 14y ago

Just to reiterate what bz said for emphasis: it wasn't a matter of Firebug "playing ball". The choice to build afresh was made based on the direction that they wanted to go at the time and our own assessment of how we could get something reliable into the product. Also, Firefox 13 (which enters beta this week) has a bunch of nice improvements including remembering whether the HTML and Style panels are open. http://hacks.mozilla.org/2012/03/firefox-aurora-13-developer-tools-updates/ http://hacks.mozilla.org/2012/03/firefox-aurora-13-developer... We're iterating at a decent pace on these tools, so keep watching. The JavaScript debugger is coming to Aurora soon and it's shaping up quite nicely. The work behind that is going to be a big win for both the new debugger UI in Firefox and ultimately for Firebug as well.