This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 7785 - "Expiring application caches" feedback
Summary: "Expiring application caches" feedback
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: NE
Depends on:
Blocks:
 
Reported: 2009-10-01 13:48 UTC by Anne
Modified: 2010-10-04 14:46 UTC (History)
4 users (show)

See Also:

Attachments

Description Anne 2009-10-01 13:48:05 UTC 
If you have application and application' that both use the same manifest and therefore the same application cache but different cookies. Is it the idea that the cache is removed when the cookie expires or when it is explicitly removed for the origin? A little more hints would be appreciated.
Comment 1 Ian 'Hixie' Hickson 2009-10-18 23:46:28 UTC 
I've tried to clarify the text.
Comment 2 contributor 2009-10-18 23:46:55 UTC 
Checked in as WHATWG revision r4173.
Check-in comment: Clarify the issue regarding appcaches and cookie UI.
http://html5.org/tools/web-apps-tracker?from=4172&to=4173