Re:A new set of Firefox Developer Tools features
by acdha on Sunday August 03, 2014 @04:43PM
(#8129121)
When talking as complicated as the developer tools it's not helpful to pronounce a sweeping judgement like "subpar" based on a single niche feature. Are the Chrome tools subpar because they lack support for easily seeing which fonts were used on an element?
[ Parent
| on HN ]
Re:A new set of Firefox Developer Tools features
by MaxGabriel on Sunday August 03, 2014 @11:47PM
(#8130220)
In chrome you can see the font used under the "computed style" tab on the right.
(This isn't meant to contradict your point—you were obviously using an arbitrary example—just thought you should know).
If anyone's aware of how, I'd like to know how to do this in Safari web inspector.
Re:A new set of Firefox Developer Tools features
by altano on Monday August 04, 2014 @01:09AM
(#8130426)
Actually that's not correct. The computed styles pane isn't telling you what font is being rendered. The Firefox Font Inspector is telling you what is actually being rendered on the screen. This is impossible to do with IE and Chrome.
Try it out: Specify a font not on your system. Chrome will show you that font while Firefox will tell you what fallback is being uses.
Re:A new set of Firefox Developer Tools features
by mh- on Monday August 04, 2014 @04:36AM
(#8130836)
that's not correct.
Chrome will show the truly rendered font from your system - the full name, even (i.e. Verdana Italic).
I've taken a quick screen capture, where I've followed your steps by requesting a non-existent font and causing Chrome to fall back:
http://i.imgur.com/C6IJyF6.png
FYI, I'm using Chrome on OS X..
Version 38.0.2107.3 dev (64-bit)
Re:A new set of Firefox Developer Tools features
by acdha on Monday August 04, 2014 @10:10AM
(#8131780)
Thanks – looks like that was added about a year ago and I obviously haven't needed it in awhile:
Re:A new set of Firefox Developer Tools features
by Kiro on Sunday August 03, 2014 @05:18PM
(#8129207)
Fair point, even though I said "for example". There are a lot of other things I think are lacking, mostly UI issues which I find unintuitive, but I wanted to bring up a concrete example which is a real deal breaker for me.
Re:A new set of Firefox Developer Tools features
by szatkus on Sunday August 03, 2014 @06:43PM
(#8129434)
Not only a single feature. Developer tools are worse in almost everything. Last time I used them (few weeks ago) I wanted to throw my rig throught a window after few minutes. Firebug saved the day.
Re:A new set of Firefox Developer Tools features
by acdha on Sunday August 03, 2014 @09:16PM
(#8129804)
Did you actually file bug reports for specific improvements? I use both heavily and have run into good and bad experiences with each — you have to talk about specific features before you can meaningfully compare anything. Is Responsive Design Mode better or worse than Chrome's debugger? Depends entirely on what I need to do.