Mozilla keeps changing the dev tools while the WebKit inspector remains fairly consistent. I no idea how to quantify it, but I just prefer the inspector, by a long shot. The networking tab and DOM inspector are brilliant.
Changing or improving?
Designing Tools
31–40 of 53 posts
Re: Designing Tools
#32I'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.
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
Re: Designing Tools
#33Earlier quoted context omitted.
Actually I don't think it does for values. I just tried to 'change' the value of a font CSS property on Hacker News from Vedrana to something else and it didn't offer any font names.
What do you expect? Should it show every possible font you can type into the property? Just the fonts installed on your machine that other people may not have? Just any property that has a preset number of values show up as options as you type. The difference is that Chrome shows a dropdown list while with Firefox you have to sort of remember the values as it does an autocomplete. I see no reason Firefox couldn't off…
[deleted]
Re: Designing Tools
#34I recently tried switching to Firefox at the place I'm currently freelancing at. Not too much front-end stuff going on, just a bit of CSS here and a bit of JS there. The two little things that annoyed me most: When inspecting an element, the element is per default collapsed (i.e. it's children are not shown). Often, I want to see the children as well - one more unnecessary click. This may be a good design decision if…
The contrast for the selected node in the markup tree is being updated here: https://bugzilla.mozilla.org/show_bug.cgi?id=968315.
Re: Designing Tools
#35Earlier quoted context omitted.
I don't disagree :) Thanks for your feedback, I think determining sensible defaults for what to show in the console is a good discussion to have!
I just want Mozilla Firefox to be better :) What language are you guys writing Dev Tools? I'd love to be able to help out, but I'm not too great with C++?
It's mostly JavaScript. Take a look at https://wiki.mozilla.org/DevTools/GetInvolved and https://wiki.mozilla.org/DevTools/Hacking for more information
Re: Designing Tools
#36I'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).
Re: Designing Tools
#37I recently tried switching to Firefox at the place I'm currently freelancing at. Not too much front-end stuff going on, just a bit of CSS here and a bit of JS there. The two little things that annoyed me most: When inspecting an element, the element is per default collapsed (i.e. it's children are not shown). Often, I want to see the children as well - one more unnecessary click. This may be a good design decision if…
The contrast for the selected node in the markup tree is being updated here: https://bugzilla.mozilla.org/show_bug.cgi?id=968315 .
Awesome! Thanks for making my day :)
Re: Designing Tools
#38I recently tried switching to Firefox at the place I'm currently freelancing at. Not too much front-end stuff going on, just a bit of CSS here and a bit of JS there. The two little things that annoyed me most: When inspecting an element, the element is per default collapsed (i.e. it's children are not shown). Often, I want to see the children as well - one more unnecessary click. This may be a good design decision if…
I just tried inspecting an element in Chrome and it didn't automatically expand to show the children. That's the behavior I would have expected. Interesting that it behaves differently for you. Are you sure you're not inspecting the child, thinking you are inspecting the parent, which would appear to be expanded in that case? Firefox offers a dark theme in the inspector's settings, maybe try that. I personally don't…
Hrm. Maybe the difference I'm noticing is that if I click on text, Chrome will expand the surrounding tag (e.g.
or ) while FF will keep it closed.
I haven't done any side-by-side testing of Chrome and FF (and am currently not working), so I can't reproduce the issue now.
Re: Designing Tools
#39Two 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 I'll try to correct it manually, but there's nothing that I can do to make me see a color that's physically impossible for me to discern.
I rely on hex codes a lot, and I do my best to develop UIs that I can navigate with ease, and won't hurt others that are colorblind. For example, whenever I see red (255,0,0) text on blue (0,0,255), or vice versa, it physically hurts my eyes.
Really the only thing that reminds me I'm colorblindness day-to-day is folding laundry. My wife color-coordinates her clothes in her closet, so when I hang them up, it's a crap shoot. She often comes to me with a new article of clothing and says, "So I can find this later, what color do you think this is?" I'm usually wrong. C'est la vie.
Re: Designing Tools
#40Earlier quoted context omitted.
Actually I don't think it does for values. I just tried to 'change' the value of a font CSS property on Hacker News from Vedrana to something else and it didn't offer any font names.
What do you expect? Should it show every possible font you can type into the property? Just the fonts installed on your machine that other people may not have? Just any property that has a preset number of values show up as options as you type. The difference is that Chrome shows a dropdown list while with Firefox you have to sort of remember the values as it does an autocomplete. I see no reason Firefox couldn't off…
[deleted]