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 7782 - "select an application cache" is vague
Summary: "select an application cache" is vague
Status: RESOLVED NEEDSINFO
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:
Depends on:
Blocks:
 
Reported: 2009-10-01 13:11 UTC by Anne
Modified: 2010-10-04 14:56 UTC (History)
4 users (show)

See Also:

Attachments

Description Anne 2009-10-01 13:11:50 UTC 
The definition refers to what the user wants and prefers and makes a MUST-level requirement out of that. Can this not be defined in a more deterministic way?

If not, what is the idea behind an user agent determining which application cache the user prefers and how does the user agent find out?
Comment 1 Ian 'Hixie' Hickson 2009-10-18 22:59:14 UTC 
Say the use has separate caches for:

   http://example.com/mail/
   http://example.com/calendar/
   http://example.com/blog/
   http://example.com/contacts/

...and each of them contain:

   http://example.com/images/logo

Which cache should be used if the user goes straight to the above page?