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/" target="_blank">webkit.org</a> (<a href="https://bugs.webkit.org/show_bug.cgi?id=26925" target="_blank">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>
<font color="#888888"><br>
Andrew</font>