Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

news.ycombinator.com

Post reply on HN
Print view View original

61–70 of 360 posts

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#61

Post by jmathai »

paulrouget wrote: post #41
drivingmenuts wrote: post #33

I 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.

The developer tools don't slow down Firefox if not used (lazy loaded), and the space used is very small. Firebug allows you to disable the builtin Inspector button.

> Firebug allows you to disable the builtin Inspector button.

I believe the parent was saying it should be a joint effort and all the resources should be pooled into one. I prefer Firebug as well and would love to see it get better, faster.

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#62

Post by Su-Shee »

So far I'm just not using the Developer Tools at all, because they don't give me what Firebug does.

Debugger, Inspect and Web Console just aren't working well together, aren't interegrated smoothly into each other and I hardly can get from one to the other. I can't enable ALL of them at once.

If they _were_ like Chrome's tools or Firebug I'd wish for the features of Firebug's XPath and CSS extension: input expression, get matching elements highlighted.

So, either they have to be as useful as Firebug, or throw them out to keep FF lean for users who doesn't need them anyways.

Also "keep the DevTools as simple as possible" makes absolutely no sense to me as a Web Developer - I need those tools as GOOD as possible and as USABLE as possible with a specific range of features I've come to expect from Firebug and Chrome.

I mean, I basically live with an open Firebug during work...

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#63

Post by paulrouget »

olivierbeaulieu wrote: post #53

I 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…

We have the inner architecture for "chrome" debugging (extensions debugging). This sill needs some more work though.

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#64

Post by Su-Shee »

oneandoneis2 wrote: post #47

I have to be honest - I find the developer tools a pain: They aren't even close to replacing Firebug, yet they're more obtrusive. So I can't stop using Firebug, and I can't remove the unwanted built-in menu options. So for me personally, what I'd really like to see is either one of: - Match Firebug feature for feature - Allow for the dev tools to be completely removed from the interface Sorry, but it really does come…

My needs exactly.

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#66

Post by radiac »

A menu somewhere to select the current media type would be lovely - not least for checking print stylesheets. Perhaps a drop-down at the top of responsive mode?

A nice ui for cookie management stuff (edit, delete) would be good too. Even better would be a way to manage different sets of cookies on the same site - eg per-tab cookies, or an option to save/clear/restore - to make it easier to test as different users at the same time.

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#68

Post by ed209 »

When I go in a tweak the CSS of various html elements, it would be nice to have those changes available somewhere (even if I reload). Even the ability to replay those tweaks after reloading.

I need this to be able to move that css back to my external files.

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#69

Post by Thibaut »

This 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!

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#70

Post by paulrouget »

oneandoneis2 wrote: post #47

I have to be honest - I find the developer tools a pain: They aren't even close to replacing Firebug, yet they're more obtrusive. So I can't stop using Firebug, and I can't remove the unwanted built-in menu options. So for me personally, what I'd really like to see is either one of: - Match Firebug feature for feature - Allow for the dev tools to be completely removed from the interface Sorry, but it really does come…

> They aren't even close to replacing Firebug

That's why we still work on Firebug :)

> yet they're more obtrusive

It should be better in Firefox 21.

> I can't remove the unwanted built-in menu options.

Firebug allows you to do that. But seeing the number of comments about this specific issue, I think we can do something smarter.

> Sorry it's not more constructive

It's actually a great comment :)

Post reply on HN