Hacker News Reader

Comment by Kiro | Hacker News Reader

I still think Firefox dev tools are subpar compared to Chrome's. For example the lack of a proper cookies listing. I often want to delete a specific cookie when developing. Very easy with the Resources tab in Chrome while a real hassle in Firefox.

View on HN

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?

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.

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.

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.

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.

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.

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)

Thanks – looks like that was added about a year ago and I obviously haven't needed it in awhile:

https://code.google.com/p/chromium/issues/detail?id=135489

Ok, so I'm getting downvoted but why? If there's an easy way to deal with cookies in Firefox then please enlighten me.

I don't know of one, but Firebug has a nice cookie viewer/editor. To be fair, the Chrome cookie tool seems to be useless for anything other than deleting cookies, which is why I keep the EditThisCookie extension installed.

https://chrome.google.com/webstore/detail/editthiscookie/fng...

You can use the `cookie` tool in what's called the "command line". It's been there for quite a while now: https://hacks.mozilla.org/2012/08/new-firefox-command-line-h...

Granted, it's not an actual panel in the toolbox, but it gets the job done.

Try Ctrl-i, right-arrow 3 times, then Alt-k.

Preferences > Privacy > Use custom settings for History > Show Cookies gives you a listing that lets you search by site or cookie name and sort the results, for what that's worth.

It's simpler than even that if you're worried about it on a per-site basis - right click, Page Info, Security, View Cookies. It's the same window, prefiltered by the site you're on.

Reply on news.ycombinator.com