7690 2009-09-21 17:27:24 +0000 Incompletely defined priority of fallback over explicit entries 2010-10-04 13:59:21 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC All VERIFIED FIXED http://dev.w3.org/html5/spec/Overview.html#updating-an-application-cache NE, NoReply P2 normal --- 1 nikunj.mehta ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 27416 0 nikunj.mehta 2009-09-21 17:27:24 +0000 [[ If a resource is listed in the explicit section and matches an entry in the online whitelist, or if a resource matches both an entry in the fallback section and the online whitelist, the resource will taken from the cache, and the online whitelist entry will be ignored. ]] What happens if a fallback namespace covers one of the explicit entries? 27793 1 ian 2009-09-29 08:07:43 +0000 I've tried to make the note clearer. Please reopen this bug if it's still leaving things unmentioned that you think should be explicitly called out. (Note that this note is non-normative; it's just giving a broad overview of the priority order implicit in the normative processing models. So it'll never be actually complete.) 27794 2 contributor 2009-09-29 08:08:01 +0000 Checked in as WHATWG revision r4035. Check-in comment: Try to make this note about what happens with clashes in the manifest cover more cases. http://html5.org/tools/web-apps-tracker?from=4034&to=4035 27877 3 nikunj.mehta 2009-09-29 16:24:03 +0000 Makes sense