[Webkit-unassigned] [Bug 24529] Add support in Web Inspector for examining/changing data for HTML5 offline-Web-applications (application cache)

[bugzilla-daemon at webkit.org]

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





--- Comment #32 from Michael Nordman <michaeln at google.com>  2010-05-19 11:52:39 PST ---
(In reply to comment #31)
> Its been a while, but I'll outline the "parts" I had in mind for splitting this up:
> 
> Part 1: Backend Push (to Frontend)
>   - create new files (requires updating all build files)
>   - UI boilerplate in JavaScript front-end
>   - show manifest file in Resources Panel
>   - push basic AppCache events to the frontend (status and connectivity)

A couple of comments/questions on the "show manifest file in Resources Panel" item.

Which instance of the manifest file? The (potentially old) manifest file, fetched from the cache, corresponding to the current version of the cache associated with the page? Or the (potentially different) manifest file, fetched from the network, in the act of updating the cache? I think you intend the latter but just want to be sure.

Fyi, the manifest file associated with a cache is always stored in that appcache as a cached resource, so it will be available for in the table of cached resources mentioned below.


> Part 2: Frontend Pull
>   - display a table of cached resources in the frontend UI
>   - ensure handled properly across refresh / page navigation
>   - cleanup part 1 to only show ApplicationCache when appropriate
> 
> Follow Up Improvements (would be other bugs)
>   - add buttons to the view to delete / update / etc
>   - indicate / show application cache resources in the Resources Panel
>   - improve graphic for ApplicationCache in Storage Panel
>   - output better error messages based on what went wrong
> 
> The idea behind splitting the patches up like this would be that they
> are buildable, usable, reviewable chunks. =)
> 
> I think Kavita has gone into part 2. Kavita, would it be possible to make
> a couple patches along the lines above? I assume you needed to make
> changes to my original patch (if you used it at all).

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