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

21–30 of 360 posts

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

#22

Post by padenot »

TrisMcC wrote: post #9

The JavaScript object browser mini-windows do not behave properly on Awesome, a tiling window manager. There is no way to close the windows without closing the entire web console. If I try to close the window like I close any other window, it will close the full browser window.

As a workaround, you can close and reopen the console to get rid of the object browser. I also use Awesome, and it works for me.

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

#25

Post by TrisMcC »

paulrouget wrote: post #14
TrisMcC wrote: post #9

The JavaScript object browser mini-windows do not behave properly on Awesome, a tiling window manager. There is no way to close the windows without closing the entire web console. If I try to close the window like I close any other window, it will close the full browser window.

We are already working on that (we call the "variable view"). It won't be a window anymore.

Thanks! I am running a current Nightly, do you know when this might land?

I am remarking today that on my system, Firefox must use less ram today than it did in 2005. Great work!

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

#26

Post by Mahn »

Excellent 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 performance.

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

#28

Post by finnnnnnnnnn »

I really dislike how chrome display :before & :after in the styles pane. More often than not these pseudo selectors contain quite important styling that's hidden away in the styles. Not sure how you can fix this, but there must be a better way.

Any chance you could remove the animation that appears when using the element selector? I find the flicker very distracting.

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

#29

Post by yesimahuman »

I think I'm just used to the WebKit dev tools, but I find it requires more work to get to the Script tools, etc in Firefox than Chrome. For example, in FF I have to go to Tools -> Web Developer -> Debugger to get to the debugger. I can't just get there by doing "Inspect Element".

I'd like to see all the tools combined into one mode and allow me to pop it out into a new window. If I can do that right now, it's just not intuitive.

Also, it'd be great if FF pushed people away from Firebug, as I didn't know FF had built in tools and I was resorting to Firebug each time.

Just some thoughts. Great work!

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

#30

Post by nsomaru »

waterside81 wrote: post #2

Hi Paul, how about when serving pages that are https, but contain mixed content, highlighting somewhere exactly what the offending requests are. Currently, I have to scan the network pane and see what's coming from the http:// domain, but it'd save me a few seconds if this was more automated.

this sounds like a "plugin" use case?
Post reply on HN