I understand this is probably not be the kind of feedback your team is looking for, but I haven't used Firefox for front end development since I got a Retina Macbook because I can't stand reading text anywhere in Firefox. Before the Retina I used Firefox/Firebug all day everyday. After Retina, I jumped to Chrome.
Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
131–140 of 360 posts
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#132Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#133Make it exactly like the webkit dev tools ?
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#134I'm glad you asked! This is a good time for me to bring up something I wrote two years ago: http://news.ycombinator.com/item?id=2024164 I really wish browser makers would do this! Mozilla can lead the way. I am going to post it here for ease of reference: 1) I propose a simple mechanism to guarantee that a resource located at a certain URL is always the same. Similar to how we have https:// blabla, and the user agent…
You are reinventing ETags.
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#135Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#1361) 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).
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#137Honestly, the absolute best thing you could do for any dev, is lighten the footprint FF currently has on my ram, and continue to improve the api for add-ons/plugins. The more stable, extensible and fast FireFox is, the more useful I will find it for development. But if more kludge is added to it, and it continues to get slower/bigger, the less likely I am to continue to use it, regardless of what amazing plugins are…
I thought that the latest browser tests showed that FF used less ram than Chrome. http://lifehacker.com/5976082/browser-speed-tests-chrome-24-... Unfortunately, reputations stick.
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#138I'm currently on FF 22.0a1 and I can't find the ability to dock the tools to the left/right. I know I used to be able to. Whether that option is present or not, I think that it is part of a bigger issue, customization. I would love to have the ability to customize the hell out of this, either from a gui or code
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#139This is a big request: Improve "design in the browser" capabilities. i.e. pushing CSS/HTML and maybe JS changes made in Dev Tools back to the source files without manual shenanigans in the middle. I probably waste more time copying CSS / HTML tweak diffs from the browser back into the related source files than anything else with in browser dev tools. Due to the nature of 'losing changes' if I happen to hit refresh or…
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#140I 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…