Live data from Hacker News

Designing Tools

blog.mozilla.org

41–50 of 53 posts

Re: Designing Tools

#41
post #11
post #8

Earlier quoted context omitted.

FWIW, you have pretty fine grained control over what appears in the console (CSS, JS, Logs, etc.) as well as the level of logging (Error, Warning, Log)... see the dropdown buttons at the top of the console tab :)

True, but default choice is SPAM WITH CSS REFLOWS, YAY! EDIT: Another thing, there needs to be a font shape difference between input and output. Basically, you should be able to tell if something is input or output without looking into the arrows to the side.

Defaults are being altered to produce less spams as we speak : https://bugzilla.mozilla.org/show_bug.cgi?id=966692

Re: Designing Tools

#42

I like FF dev tools a lot, yet there is some stuff there that could be better: - no call stack(?) - breakpoints are a bit of a hit or miss, especially when callbacks are involved. - http request monitoring is a bit messy - you see the request in the console, you can click on them, but the resulting dialog box only offers basic info, without even an option to go to the clicked url directly. In network panel the functi…

Response tab can now have any amount of width in Nightlies. https://bugzilla.mozilla.org/show_bug.cgi?id=956357

Re: Designing Tools

#43
post #2

Two questions: To those who are color blind, how do you overcome color blind in software? Do you guys have software to help changing color on your computer? Should and will Firefox address that kind of problem? Nightly defaults to the dark theme. I like old white theme. https://bugzilla.mozilla.org/show_bug.cgi?id=947242 why do we choose the dark theme over the white theme? I am not color blind but I use computer typ…

I'm not severely colorblind, but I'm red/green colorblind, and I hope I can help you out. I don't use software to change color on my computer--there's nothing that I can change it to that will look more like whatever y'all see it as--I just simply can't see that color. I've lived with my colorblindness for three decades, so it's not like I'm trying to get used to it still. Sometimes the contrast is off on things, and…

Thanks for the comment, we always try and cater to as many of our users as possible. If you've used our tools, are there particular areas that cause more trouble than others? Do you find the dark or light theme easier to navigate (available in Nightly builds right now)? Would love to hear how our tools can be improved in this regard! Feel free to email me at darrin[at]mozilla.com if you'd rather not post on HN.

Re: Designing Tools

#44
post #32
post #30

Earlier quoted context omitted.

I second that. Also, in Firebug, you can see the padding clearly (it's in a different color) when you hover over an element with the inspector. This is not the case in the Firefox Development Tools. It's still possible to get the same information from the Box Model view but it's just nice to be able to see it visually on the page.

This feature is being worked on, and is close to landing: https://bugzilla.mozilla.org/show_bug.cgi?id=663778

Awesome!

Re: Designing Tools

#45
Does anyone know if I can add custom classes to the insector in FF? I currently use the Aurora build and can't seem to find a better way to do it. Chrome DevTools have a handy little '+' that lets me add any class I want to the stylesheet... but in Firefox I am limited to only editing existing classes.

This is a minor annoyance but it's enough to keep me from being fully ready to switch to FF.

Re: Designing Tools

#46
post #4

Earlier quoted context omitted.

Yes, the current dark theme does not have high enough contrast. There is a bug opened to switch to higher contrast colors in the dark theme here: https://bugzilla.mozilla.org/show_bug.cgi?id=971418 (and this will likely be uplifted to Aurora after landing).

There is a light theme in Aurora right now.

FWIW, I'm colorblind and I use and prefer the dark theme.

Also, (warning this gets a little hand wavy) most pages on the web are light, so the light theme blends in. It is useful to have that contrast by default. Easier to make a distinction visually, and also "self xss" is deterred a little because the devtools are more obviously not part of facebook or whatever.

Re: Designing Tools

#47

I like FF dev tools a lot, yet there is some stuff there that could be better: - no call stack(?) - breakpoints are a bit of a hit or miss, especially when callbacks are involved. - http request monitoring is a bit messy - you see the request in the console, you can click on them, but the resulting dialog box only offers basic info, without even an option to go to the clicked url directly. In network panel the functi…

no call stack(?)

There are breadcrumbs across the debugger's toolbar for quick always available access, or there is a tab to display the whole stack at once next to the sources tab on the left sidebar.

breakpoints are a bit of a hit or miss, especially when callbacks are involved.

If you have a test case / url / steps to reproduce, please file a bug: https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&c...

We can't fix what we can't detect.

So kudos to them for all the hard work.

Thanks :)

Re: Designing Tools

#48
post #36

I'm trying to move from firebug to the native firefox development tools. The one thing I miss is the network tab doesn't render formatted html or datastuctures, it just text dumps (firebug give you the option and shows json, html, formatted). That and it seems the network tool turns on when you click the tab, but no way to turn off. Other than that I really like the tools.

Please add "formatted JSON" that start with "for(;;)" or "while(1)" ...a common technique. Chrome DevTools supports this, and both Facebook and Google use it in their XHR/AJAX responses (so do I).

Filed https://bugzilla.mozilla.org/show_bug.cgi?id=978206 for you.

Re: Designing Tools

#49
Last time I used the Firefox Developer Tools (on 27.0.1), it was unusably slow, caused the browser to crash several times, and very unintuitive even when it was working as (I assume) it was intended to. Are there improvements since v27?

Re: Designing Tools

#50
The two reasons I have to stick with Chrome are Batarang for AngularJs debugging and chrome dev tools for NodeJs debugging with node-inspector. I haven't found any alternatives to these in Firefox, but would switch in a flash if there was.
Post reply on HN