Actually, I believe the spec does address the question in the following passage (this is in the manifest parsing algorithm):<br><div> </div><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
If mode is "explicit"</blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
Resolve the first item in tokens, relative to base URL; ignore the rest.</blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
<br></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
If this fails, then jump back to the step labeled "start of line".</blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
<br></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
If the resulting absolute URL has a different <scheme> component than the manifest's URL (compared in an ASCII case-insensitive manner), then jump back to the step labeled "start of line".</blockquote>
<blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
<br></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
<b>Drop the <fragment> component of the resulting absolute URL, if it has one.</b></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
<br></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
Add the resulting absolute URL to the explicit URLs.</blockquote><div><br></div><div>So it must be an implementation issue.</div><div><br></div><div>Cheers,</div><div>Maria </div><br>On Mon, Jul 6, 2009 at 3:37 PM, Andrew Grieve <<a href="mailto:agrieve@google.com">agrieve@google.com</a>> wrote:<br>
><br>> The current behavior in Webkit is for URL fragments to be stored in the<br>> URLs for master entries. I believe this to be a bug in Webkit, but cannot<br>> determine from the spec if this is or not.<br>
><br>> Example:<br>><br>> 1. Navigate to: <a href="http://www.thecssninja.com/demo/offline_webapp/#foo">http://www.thecssninja.com/demo/offline_webapp/#foo</a><br>> 2. Go offline<br>> 3. Do a browser refresh and ensure the page refreshes from AppCache.<br>
> 4. Change the URL hash to #bar<br>> 5. Do a browser refresh and notice that it fails to load.<br>><br>> I've filed a bug on <a href="http://webkit.org">webkit.org</a> (<a href="https://bugs.webkit.org/show_bug.cgi?id=26925">https://bugs.webkit.org/show_bug.cgi?id=26925</a>)<br>
> regarding this, but realized that the spec is unclear about what is<br>> expected here. Since fragments are not sent to servers, I can't see<br>> why they would be included in the master entry URLs as they make no<br>
> difference in the content that is served.<br>><br>> Anyone know if the spec does in fact address this issue?<br>><br>> Andrew<br>