971672 - integrate app cache to storage inspector

Status: RESOLVED WONTFIX

(DevTools :: Storage Inspector, defect)

Description

[Soledad Penades [:sole] [:spenades]]

Yes, the AppCache "is no longer a douchebag" http://flailingmonkey.com/application-cache-not-a-douchebag ... but this way of debugging appcache entries doesn't work when you have more than one or two entries. Starting with the double command prompt stacked one above the other (the console, and the developer toolbar) and continuing with the pop up with all the list of entries. Not the best interface :-)

Could we have some sort of about://app-cache - a little bit like what you get in Chrome with chrome://appcache-internals/ ? (attaching screenshot because an image is worth 1K words) - it'd be like a refinement of about://cache, or maybe another iteration on about:cache?device=offline (but I don't know if that's part of Firefox-Core or Firefox-DevTools).

And please link to it somewhere that I can click from DevTools, not obscured under some magic URL or started from a developer toolbar that I never remember how to bring up and have to look up in a blog post all the time.

Because otherwise we always have to end up debugging AppCache stuff with Chrome, and that's not exactly ideal as we don't have a chance to debug AppCache + Gecko stuff.

Comment 1

[Soledad Penades [:sole] [:spenades]]

Attachment: app cache internals in Chrome

Comment 2

[Paul Rouget [:paul]]

Optimizer, what do you think?

Comment 3

[Paul Rouget [:paul]]

I'm wondering if this should be part of the storage inspector.

Comment 4

[Girish Sharma [:Optimizer]]

Yeah, it should be. Also, the hierarchy (url > entries) is similar to other storages so that is in line :)

Comment 5

[Mike Ratcliffe [:miker] [:mratcliffe] [:mikeratcliffe]]

But we already have about:cache ... clicking on "list cache entries" under "Offline cache device" brings up appcache information.

Comment 6

[Mike Ratcliffe [:miker] [:mratcliffe] [:mikeratcliffe]]

Of course, making the same stuff available in the storage inspector would be awesome.

Comment 7

[Girish Sharma [:Optimizer]]

So we already have what chrome has :)
But yeah, we can still put things into Storage Inspector.

Comment 8

[Soledad Penades [:sole] [:spenades]]

If we have "what chrome has" why can't I use it in a comfortable manner as I can in Chrome? I can't delete entries from a particular domain, for example. Also I can't see the information about an entry either (it's broken, see https://bugzilla.mozilla.org/show_bug.cgi?id=861866)

It's OK to be optimistic, but I'm afraid that saying we have feature parity is being delusional :-/

Comment 9

[Paul Rouget [:paul]]

(In reply to Soledad Penades [:sole] [:spenades] from comment #8)
> If we have "what chrome has" why can't I use it in a comfortable manner as I
> can in Chrome? I can't delete entries from a particular domain, for example.
> Also I can't see the information about an entry either (it's broken, see
> https://bugzilla.mozilla.org/show_bug.cgi?id=861866)
> 
> It's OK to be optimistic, but I'm afraid that saying we have feature parity
> is being delusional :-/

It's not what we meant (bug is still open, not wontfix).

Purging app cache is hard. Very hard. And I believe that we can implement a good tool in the storage inspector. We'll need some time though.

Comment 10

[Girish Sharma [:Optimizer]]

mass component move . filter on #MassComponentMoveStorageInspector