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 7706 - This section should reference "matches a fallback namespace" in step 3.
Summary: This section should reference "matches a fallback namespace" in step 3.
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: NoReply
Depends on:
Reported: 2009-09-23 09:30 UTC by contributor
Modified: 2010-10-04 14:28 UTC (History)
5 users (show)

See Also:


Description contributor 2009-09-23 09:30:42 UTC

This section should reference "matches a fallback namespace" in step 3.

Posted from:
Comment 1 Ian 'Hixie' Hickson 2009-09-29 09:20:00 UTC
Why? The "matches..." algorithm is for the generic case of matching any appcache; the network model's third step is about when loading from a cache that is already selected.
Comment 2 Anne 2009-10-19 09:05:10 UTC
This is now step 4.

First it says "and there is a fallback namespace in the application cache that is a prefix match"

Then it says "the resource of the fallback entry corresponding to the matched namespace".

The problem here is that it is at best ambiguous what "matched namespace" refers to.
Comment 3 Ian 'Hixie' Hickson 2009-10-20 00:49:54 UTC
Ok, tried to fix...
Comment 4 contributor 2009-10-20 00:50:49 UTC
Checked in as WHATWG revision r4180.
Check-in comment: Try to make this less ambiguous.
Comment 5 Maciej Stachowiak 2010-03-14 14:51:40 UTC
This bug predates the HTML Working Group Decision Policy.

If you are satisfied with the resolution of this bug, 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:

This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.