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

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=41637





--- Comment #7 from Michael Nordman <michaeln at google.com>  2010-07-08 17:34:45 PST ---
(In reply to comment #6)
> (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.

After the delete i described, reloading the page *would* create a new cache group and download all over again (yada yada). Any other pages however still associated with the old cache would still be non-functional wrt sub-resource loading.

> 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.

I think you just tacked on another automated step, the delete function i described earlier + an auto reload the page step. For my tastes, the auto reload part would be doing more than I want. I can easily enough reload the page on my own.

The "obsolete" semantics are an option. I didn't use those semantics in chrome because stuff has to linger in memory and on disk until pages using caches in that group go away of their own accord. I wanted to make it go away NOW.

> > "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.

Another big difference is that there is no auto-reload of the page being inspected.

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