Hacker News Reader

Comment by badman_ting | Hacker News Reader

Does anyone know how to look at cookies? I seriously cannot find cookies in the Firefox dev tools, the new interface is so irritating and disorienting. Plus I think everyone is just trying to collectively pretend that cookies don't exist anymore.

View on HN

  - open dev tools
  - click on Network tab (far right)
  - make a request (e.g., reload current page)
  - click on one of the entries in the list
  - there's now a tab for cookies on the right

There is also a work in progress to add a better interface for inspecting storage (including cookies): https://bugzilla.mozilla.org/show_bug.cgi?id=926449

Jesus christ. Thank you, though.

It's pretty much the same as Chrome. One thing I see in Firefox that I don't in Chrome, though, is the "edit and resend" feature, which lets you edit a request and resend it. It's pretty cool.

Little known feature: There's also a "cookie" command in the GCLI. Shift-F2 to bring up the command line, type "help cookie".

FF Dev Tools have serious usability quirks vs FireBug that prevent me from considering it for anything but FFDT-specific functionality.

I also agree that I find FFDT unusable compared to Firebug or Chrome dev tools. I find it hard to pinpoint exactly what it is about it though.

There are lots of things, which is why it's hard to pinpoint. It's a death by thousand cut things.

The unusable console printing of objects was a big one, glad to see it's finally getting somewhat rectified.

(OTOH, Safari has taken the cake as well as the whole kitchen with the new back-asswards development tools, going from perfectly usable ones to the current utter garbage while Chrome's gets better by leaps and bounds)

(meanwhile the one bloody thing they could have, namely Xcode's awesome breakpoint actions pane, they don't integrate)

I'm guessing the browser devtools space is being subjected to the user-hostile practice of "product differentiation."

I'm sure it is, but that's not much comfort when you're forced to use that POS because it's (AFAIK) the only remote debugger for Safari/iOS, and it was previously prefectly serviceable.

I used to agree with you until Firefox 25 or so. In fact, I always tested mainly in FF (as that is my main browser) but I'd switch to chrome when I needed any sort of debugging or inspecting more complicated than reading the console.

But in the past couple revisions, I've found myself going to Chrome less and less often. Hardly ever any more with 27, and never first. Mozilla is making constant improvements and I'm quite happy with them. The debugger seems very solid to me inspector is just as good as chrome. The Chrome profiler's flame-maps are pretty awesome though.

If you just want a list of cookies, I usually look at them from the preferences (Privacy -> Show Cookies) and then use the search to narrow down to the domain I'm looking at. Not quite as good as Chrome's resource browser, but it works.

Reply on news.ycombinator.com