This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
There is a long section in HTML5 describing loading of ambiguous entries: ------------------- If a resource is listed in the explicit section or as a fallback entry in the fallback section, the resource will always be taken from the cache, regardless of any other matching entries in the fallback namespaces or online whitelist namespaces. When a fallback namespace and an online whitelist namespace overlap, the online whitelist namespace has priority. The online whitelist wildcard flag is applied last, only for URLs that match neither the online whitelist namespace nor the fallback namespace and that are not listed in the explicit section. ------------------- It would be helpful to mention master entries here, as well. I've seen people list https://www.their_site.com in NETWORK section, and expect all resources not listed as explicit ones to be loaded from the network, including the HTML document.
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments.
Checked in as WHATWG revision r5813. Check-in comment: clarify that pages with a manifest='' always get served from their cache. http://html5.org/tools/web-apps-tracker?from=5812&to=5813
mass-move component to LC1