[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 bugzilla-daemon at webkit.org
Wed May 19 12:24:26 PDT 2010


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





--- Comment #33 from Joseph Pecoraro <joepeck at webkit.org>  2010-05-19 12:24:24 PST ---
> 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.

I haven't followed changes in the spec recently, but I most certainly
mean the most up to date. Doesn't the browser, if online always? fetch
the manifest file and check:

  1. if there was an error it could be
    - 404/401 or something like that would show up as obvious
    - a parse error, the resource data would still be useful
  2. if it has changed
    - resource data would still be useful
  3. if it was byte-for-byte identical, or 304, or equivalent
    - resource data would still be useful
  4. if offline, uses the manifest
    - manifest data would be useful

So in all of these cases it looks like the best thing to do is show what
we got from the network! In the case of 3 we may have to show the
contents from a cache (like we already do for typical cached resources).

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