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

Designing Tools

blog.mozilla.org

Post reply on HN
Print view View original

11–20 of 53 posts

Re: Designing Tools

#11

Post by Ygg2 »

dhenein wrote: post #8
Ygg2 wrote: post #7

Earlier quoted context omitted.

Good point, I was surprised it didn't work like that. Guess it's one of those little things. Personally, I think that console could do some work. Chrome console is top notch, and there is too much noise in FF version, with CSS and other stuff.

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.

Re: Designing Tools

#12

Post by Ygg2 »

Optimizer wrote: post #6
slowmotiony wrote: post #5

The main reason I don't switch to Firefox's dev tools is whenever i write a css attribute in the inspector, Chrome will present me a nice list of possible values I can choose, while Firefox just sits there patiently until I start writing. I don't always remember all the values and this really breaks my workflow.

Firefox also provides a suggestions list for CSS properties and values in the rule view and the markup view of Inspector since Firefox 25.

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.

Re: Designing Tools

#13

Post by evilpie »

Ygg2 wrote: post #12
Optimizer wrote: post #6

Earlier quoted context omitted.

Firefox also provides a suggestions list for CSS properties and values in the rule view and the markup view of Inspector since Firefox 25.

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.

Well I guess that was kind of unlucky. clear, color etc. all work, it just can't do font suggestions.

Re: Designing Tools

#14

Post by dhenein »

Ygg2 wrote: post #11
dhenein wrote: 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.

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!

Re: Designing Tools

#15

Post by Ygg2 »

dhenein wrote: post #14
Ygg2 wrote: post #11

Earlier quoted context omitted.

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.

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++?

Re: Designing Tools

#17

Post by dhenein »

polskibus wrote: post #16

How do you turn on the memory tab in FF (like the one shown in the article) ? I have Aurora and I can't find an option to do that.

Sorry, that is just a prototype for now! We are in the process of designing and planning the memory (and performance) tools, which should hopefully be available sometime this year.

Re: Designing Tools

#18

Post by Siecje »

When viewing a local .html file on your computer you should be able to edit the entire page as html and have the browser automatically update and you should be able to save to the file you opened.

Re: Designing Tools

#19

Post by CookWithMe »

I 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 tools are running on a laptop screen inside the main browser window, but I'm using two monitors and the tools take a whole screen.

Related, my main monitor has a terrible (=no) contrast between white and light gray if viewed from some angles. Often, if I inspect an element, I'm missing the highlight (light gray on white)... Yep, I should probably play with the monitor settings, although FF seems to be the only tool I have this problem with.

These are obviously not big issues and I don't miss the Chrome tools too much, so I'm sticking with FF. Keep up the good work!

Re: Designing Tools

#20

Post by pjmlp »

What I miss in FF developer tools and makes me use Chrome Dev Tools instead:

- Working on the console is a nice REPL experience with code completion and data structure navigation, almost similar to a Smalltalk/Lisp workspace

- I can work on the console whenever I feel like it and do not have to pause the debugger

- More freedom to place breakpoints in the whole browser stack (events, html changes, ajax calls, ...)

- Code and event profiling

- Reformatting minified JavaScript

- Tooling for navigation the whole set of resources and local databases being used by the browser

Post reply on HN