An SSL MITM "proxy" a la Burp, but built into Firefox (or Firebug). It would be nice if it allowed re-writing (both manually and programmatically) requests and responses (including headers) on the fly, substituting files, etc.
Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
91–100 of 360 posts
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#92I'd greatly appreciate a performance monitor that is tab specific or even code specific. If you can dial down that one of my methods are using up 80% of my memory, please let me know. Or if the reason my page keeps crashing is because some knucklehead is still using flash poorly for ads, then I need to know that. From that, if you can "label" sites or ad styles or script styles that are known to perform poorly, that…
We have plan for performance tools. See: https://groups.google.com/forum/?fromgroups=#!topic/mozilla....
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#93I would say make Firefox as light and fast as possible by keeping ALL developer tools as addons. Most users aren't going to need them at all, so it's just eating up space for no reason. I personally prefer Firebug over Inspector, so I would rather see you throw more resources into integrating it fully with FF.
That new Inspector thing is really annoying. I always accidentally open it instead of Firebug. From a developer stand point, Firebug stills beat all other browser dev-tools by a mile and is the main reason I still have Firefox on my dashboard.
You can turn off the built-in Inspector by going to about:config. There's an option in there (I forget the name of it off the top of my head... probably something like "inspector"!) and you can change the Boolean value to 0 and it will no longer appear in the context menu.
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#94This 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…
This is quite honestly the best new feature we could be given. It's not an easy task, but such a tool could save millions of man-hours.
Mozilla guys: if you implement this--even partially--I'll switch back to Firefox in a heartbeat.
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#95I think something that would be useful as a dev tool in FF, which only chrome right now has a decent tool for is restful url testing, similar in part to https://chrome.google.com/webstore/detail/advanced-rest-clie... I haven't seen anything even remotely similar for FF, maybe a optional plugin for this kind of tool, it would make my development process much quicker for the client-side code which is being used for restful interfaces. especially if we can maintain our session when submitting information.
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#96Excellent initiative! I'd personally kill for a tool akin of Chrome's timeline, where to debug performance issues not related to javascript, like rendering e.g. things that trigger a complete screen redraw and whatnot. I'd really like to see this happen because at the moment if an app is super snappy on Chrome but slow on Firefox and javascript is not the culprit, I'm left basically to guess how to improve the perfor…
We have a plan for performance tools: https://groups.google.com/forum/?fromgroups=#!topic/mozilla....
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#97I think something that would be useful as a dev tool in FF, which only chrome right now has a decent tool for is restful url testing, similar in part to https://chrome.google.com/webstore/detail/advanced-rest-clie... I haven't seen anything even remotely similar for FF, maybe a optional plugin for this kind of tool, it would make my development process much quicker for the client-side code which is being used for res…
Better auto-complete for css fields for the css editor in the new FF, such that it's on par with the firebug auto-complete functionality in the dom/css inspecter
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#98What I would love to see are improved privacy options. Whenever I come across https://panopticlick.eff.org it serves as a reminder that there could be much more done to reduce the footprint.
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#99This is my wish list: (I'm running Firefox Beta) - Show ::before/::after pseudo elements in the DOM inspector. - An option to clear the web console on page reload. - An option to hide assets requests / show only ajax requests in the web console. - A "Storage" tab for viewing cookies, localStorage, applicationCache, etc. - Merge the Developer Toolbar with the DevTools. Thanks!
I agree with all of that (especially with 1, 2 and 5).
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#100My suggestion is to take a look at this plugin and make everything about it better and faster:
http://chrispederick.com/work/web-developer/
I use this thing several hours per day.