News for hackers. Stuff that matters.
Re:Firefox Developer Tools and Firebug by jfaucett on Tuesday October 08, 2013 @03:42PM (#6517330)
First Id like to say Im a huge fan of firefox and really like what mozilla does.

So I would love to be able to use the developer tools - but for me they're still not quite there (but getting close). Here's some things Id like to see, and then I think I could change over from chromes devtools completely, wonder what other devs think?

1. speed (becoming less of a problem)

2. edit html in elements inspector, also dynamically creating styles: - What I like about chromes devtools is the fact that I can completly alter my html page via the elements panel (styles and html) very fast, also auto-expanding to the selected element and seeing its surroundings is nice.

3. network panel still not as good as chromes (imho) - mainly because I cant enlarge the detailed inspection of each listed http request.

4. too intrusive (popups for javascript editor) - make it more compact and use less space, also I like tabs (that are optionally detachable) instead of windows.

And thats it, these are the only reasons for me personally, why I dont use firefox as my development browser of choice.

But again Id like to say the work the mozilla devteam is putting into the devtools makes me think its just a matter of time until I can finally go back to mozilla :)

Re:Firefox Developer Tools and Firebug by ep103 on Tuesday October 08, 2013 @04:09PM (#6517495)
1) Will be improved in next release, was a platform specific issue, apparently.

2) You can do this already. It works just about the same as chrome dev tools, create a new rule to add a new css rule, etc.

3) I would like this too.

Re:Firefox Developer Tools and Firebug by jfaucett on Tuesday October 08, 2013 @04:23PM (#6517583)
- as far as #2 goes, I have to open up the style editor tab (then i find myself switching back and forth, is it possible to add rules in "rules" panel inside the "inspector" tab to avoid the switching? Also, in my build (maybe a week old or so), When I right-click a node in the inspector I only have copy html options and delete node, no edit html - does a more recent release have this - that would be awesome.
Re:Firefox Developer Tools and Firebug by ep103 on Tuesday October 08, 2013 @07:27PM (#6518545)
yeah, from the HTML tab you can just right click the style on the right hand side of the window and click New Rule. It'll assume that you're attempting to write a new rule for the type of element you currently selected, but just tab to that box and you can change it.

Note, when I say style here, I mean style on the HTML tab, not the style tab itself.

Re:Firefox Developer Tools and Firebug by sgarrity on Tuesday October 08, 2013 @06:53PM (#6518381)
re: #2

You can edit all of the individual components of a tag (attributes, the tag itself, add new attributes, etc.), but you can't edit/select the entire tag or child tags at once as you can in Firebug.

This can be really powerful, because when you can edit an entire tag including the open/close brackets, you can type in whole new tags or paste in a blob of new HTML.

This bug was the closest I could find: https://bugzilla.mozilla.org/show_bug.cgi?id=777009

Re:Firefox Developer Tools and Firebug by bgrins on Wednesday October 09, 2013 @09:29AM (#6521079)
Here is the bug for the "Edit as HTML" feature: https://bugzilla.mozilla.org/show_bug.cgi?id=895561.
Re:Firefox Developer Tools and Firebug by integricho on Wednesday October 09, 2013 @02:10AM (#6519672)
1. Logging of objects and arrays should produce a similar output like in chrome or firebug, currently the [object Object] like representation is not really helpful, I have to inspect all of them to find what I'm looking for.

2. +1 for the above mentioned network panel details, I agree, and the URL of the request can not be copied currerntly, that's mean :)

3. +1 for the need of stacktrace, like in chrome, that's sooo needed

4. A shortcut in it's settings for disabling the cache

Re:Firefox Developer Tools and Firebug by jamesgeck0 on Tuesday October 08, 2013 @06:49PM (#6518364)
3. Yes. If I get a 500 error from my web application with a stacktrace in the html, it's really hard to read it in the source in the Firefox inspector. Webkit dev tools will both show the source and render it.