5 ms·
> 1. Please either respect the font sizes I set in the Firefox Preferences, or add a setting to change the font size inside the devtools. Currently the inspecto
by mnemonik 13y ago
> 1. Please either respect the font sizes I set in the Firefox Preferences, or add a setting to change the font size inside the devtools. Currently the inspector and style panel on the right, among others, seem to use a fixed size that is just tiny enough to be seriously annoying.
We have a bug open for respecting the system font size here: https://bugzilla.mozilla.org/show_bug.cgi?id=760825 https://bugzilla.mozilla.org/show_bug.cgi?id=760825
In the meantime, you can change the devtools font sizes with Cmd+<+> and Cmd+<->
> 2. All URLs everywhere should be clickable, middle-clickable, and have a context menu for these actions as well as other common stuff like copying it to the clipboard. Last time I checked there was no way to get the full URL of a stylesheet, clicking on it would only open the Style Editor which doesn't seem to expose the URL anywhere either.
Agreed, we have various bugs open in different bugzilla components. Will ping people about it.
> 3. Sometimes the devtools get stuck somehow, i.e. I suddenly can't open the Inspector anymore, or the console wwill stop displaying messages. This happened at least up until FF25, at which point I gave up and installed Firebug again.
Do you want to try out Aurora again? I recall a couple issues like what you described that got fixed (one of which was my fault, woops!) and I'd love to know if you are still experiencing this or if it is groovy now.
If you are still experiencing it, please file a bug!
https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Developer%20Tools https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&c...
> 4. Please support all different color syntaxes (ideally as in Firebug where I can choose my preferred format and have everything converted to it)
You mean custom syntax highlighting? Would be nice to have, but honestly probably not a priority. Everyone is very busy trying to bang out features and bug fixes, and even just the two themes we support now feel like a burden (at least to me). Hopefully we can do this sometime in the future, though!
> Otherwise it seems you're doing a great job, I just wish you would get the basics right first before adding stuff like a 3D view ;-)
Thanks! :D
For the record, the 3d view was either a GSoC project or an intern project, and hasn't really had much (basically any) maintenance burden.
On top of that, I think it is cool because it might not teach people who know about the web much, but it has the possibility to excite people who know nothing and make them want to learn more. I first got involved in web dev when I was like 10 or 11 and being able to view source was magical. Hopefully the 3d view helps give people that same feeling now days of being able to see a little under the hood and get them excited and draw them in.
Cheers!
- nnethercote 13y agomnemonik: two thumbs up for the great responses you are giving in this thread!
- mnemonik 13y agoThanks! Congrats on the low level tools team! I look forward to having more APIs to really get deep into the platform :)
- toupeira 13y agoThanks for the answer! I'll take another look at the latest Aurora. As for point 4, at the moment colors are always displayed with rgb() syntax, even if they were specified as a hex-string or with hsl() syntax in the stylesheet. In Firebug there's a dropdown menu on the style tab where you can choose between "Colors as Hex", "Colors as RGB" and "Colors as HSL".
- mnemonik 13y agoAh yes, I see! You can actually configure that via the options tab (the sprocket to the left of the console tab). Soon, we will show you the colors as they were authored by default. I can't seem to track down the bug, but I know the inspector folks have it on their radar.
- toupeira 13y agoYep just noticed it in the latest devtools blog post, the color swatches are awesome too!