Please build a remote inspection / debugging API similar to Chrome so tools like http://brackets.io can integrate with Firefox.
Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
201–210 of 360 posts
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#202Two things I would like: 1) An easy way to debug events. I find that javascript has become so non-linear it is really hard to decide where to breakpoints and what I really want is to follow an event from object to object instead. 2) An easy way to send, receive, debug RESTful Ajax queries: GET, PUT, POST, DELETE would be nice especially if it had a clever way to view and edit the requests (and responses).
Number 1:
I would love a tool that would let me set a breakpoint on an element and then show me a stack trace any time that element is modified. This would make locating a broken piece of JS in an unfamiliar code base so much easier.
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#203Look at phantom.js -- make it happen that Firefox integrates easily with the framework.
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#204Thanks for doing this post! Some things I'd like to see: * Less UI chrome. The blue bar doesn't need to be blue and element breadcrumbs don't need to be fancy styled boxes. Large elements don't even fit in them and get chopped off. * When I hit Ctrl-Shift-I the FDT open, but if I have the dialog detached it immediately loses focus and I have to alt-tab to see it. * I find Chrome's Network inspector to be very useful…
Deminifying is probably going to be standardized as source maps. That will (or should) eventually land up in all the browsers.
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#205Hey Paul. First off, thanks for reaching out to the community like this. A few things: Visualized event bindings. Would be awesome to have a visual indicator of event bindings right on the page. Color-coded bounding boxes drawn around elements with a label denoting the event type. Clicking on that box (or label in the case of an element with multiple bindings or nested elements with bindings) would direct you to the…
Last time I used the Firequery plugin for Firebug (way back in FF3), it would show the elements on the page that were also represented as jQuery objects... that plugin might be a jumping-off point for how to show visualized event bindings
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#206A thing I never understood is why writing into the console a function should show the complete body content.
The only one who do it "right" in my head is firebug: console.log(my_function) show just the function "definition", clickable to go directly in the sources at the right row.
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#207Hey Paul. First off, thanks for reaching out to the community like this. A few things: Visualized event bindings. Would be awesome to have a visual indicator of event bindings right on the page. Color-coded bounding boxes drawn around elements with a label denoting the event type. Clicking on that box (or label in the case of an element with multiple bindings or nested elements with bindings) would direct you to the…
> Visualized event bindings. Would be awesome to have a visual indicator of event bindings right on the page. Color-coded bounding boxes drawn around elements with a label denoting the event type. A bit of shameless self promotion - I wrote a bookmarklet to do that asking talking to a couple of Mozilla folks a few years back: http://sprymedia.co.uk/article/Visual+Event+2 . Source is available on GitHub: https://githu…
Thanks for the awesome tool! I've found it handy on more than one occasion to trace jQuery/vanilla JS listeners. Any plans for Dojo support?
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#208Earlier quoted context omitted.
> That's why we still work on Firebug To be quite frank, this is really ridiculous to me. Why in heck are there TWO separate developer tools for one browser that are both in-house? Supporting both tools means that neither one moves as quickly, and there's a ridiculous amount of confusion as to which one to use. Imagine the noobie developer that has cut their teeth on the elegant Chrome dev tools. Now they need to do…
Firebug isn't in house, it just has contributions from Mozilla employees.
If Firebug isn't in house then I have no idea how a Mozilla employee could justify working on Firebug while their own "official" dev tools still has such a long way to go.
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#209[deleted]
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#210I work a lot on a Firefox extension, and honestly, the absence of dev tools for addons is really painful. Developping our extension for Chrome was super easy, since all their default devtools work in extension panels as well, but in Firefox it's been a nightmare, almost no tools. We are left off in a console.log madness trying to figure out what's causing bugs. It would be soooooo awesome to have Firefox's default de…
Agreed - we've built extensions for Chrome, Firefox, IE & Safari ; Firefox and IE are on the same level with regards to debugging, that is : not pleasant. It's a shame because browser extensions have great potential : I'm increasingly turning towards them for a variety of use-cases, however currently limiting efforts to Chrome due to availability of tools.