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 7690 - Incompletely defined priority of fallback over explicit entries
Summary: Incompletely defined priority of fallback over explicit entries
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: NE, NoReply
Depends on:
Reported: 2009-09-21 17:27 UTC by Nikunj Mehta
Modified: 2010-10-04 13:59 UTC (History)
4 users (show)

See Also:


Description Nikunj Mehta 2009-09-21 17:27:24 UTC
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?
Comment 1 Ian 'Hixie' Hickson 2009-09-29 08:07:43 UTC
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.)
Comment 2 contributor 2009-09-29 08:08:01 UTC
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.
Comment 3 Nikunj Mehta 2009-09-29 16:24:03 UTC
Makes sense