[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
Fri Jul 9 14:25:28 PDT 2010


--- Comment #14 from Michael Nordman <michaeln at google.com>  2010-07-09 14:25:28 PST ---
> For a potential user who develops using ApplicationCache, they aren't concerned
> with the implementation details. They only know what the spec says, and to them
> making something "obsolete" is itself a concrete action. I don't think they would
> understand "make obsolete and delete from disk", because to them that is invisible.
> This is just like your suggestion for "Refresh" to be action "update and swapUpdate",
> that is a concrete action in high level application cache terms, not implementation
> details.

That sounds reasonable.

> To me this sounds like a very small drawback to the Chromium delete approach.
> But, its certainly in no way harmful.

Or a small feature ;)

That delete function i described is wired to different user interfaces.

Not sure which semantics are better really, both would work. With delete now semantics, contexts tied to instances will clearly stop functioning. There will be less risk of confusing context tied to a deleted cache with context tied to renewed caches. With make obsolete semantics, the manifest url will be the same for each, but if you look very closely... one will say OBSOLETE for the appacche status display and the other will say IDLE... but may be too subtle of an outcome after explicitly pressing the delete button.

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