[Webkit-unassigned] [Bug 41637] Web Inspector: Give Semantics to "Refresh" and "Delete" Buttons in ApplicationCache DataGrid

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Jul 8 16:38:55 PDT 2010


--- Comment #6 from Joseph Pecoraro <joepeck at webkit.org>  2010-07-08 16:38:54 PST ---
(In reply to comment #1)
> We have a "Delete" function in chrome which could be wired to this button. The semantics of
> that function are to immediately delete from persistent storage all of the resources associated
> with the ApplicationCacheGroup. After doing this, sub resource loads in all pages associated
> with any cache from that group will fail.

I don't see the usefulness of this type of delete. It sounds like the only way to make the
web application useful again would be to change the manifest.

I was thinking "Delete" would actually eliminate the application cache you're viewing. The
use case goal being you can use the delete button, and then refresh the page to re-download
the resources _even if the manifest didn't change_!! Is it enough to just "obsolete" the current
application cache? Considerations would include disabling the delete button when its
not appropriate.

> "Refresh" could mean, call .update() and when the update completes call .swapCache()
> if the cache status is UPDATE_READY. And then repopulate the display with the new
> contents of the updated cache.

I think this is a great idea. The difference between this an the "Delete" semantics I describe
above would be that here nothing would be re-downloaded if the manifest has not changed.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list