<br><br><div class="gmail_quote">On Mon, Jul 6, 2009 at 2:40 PM, Aaron Boodman <span dir="ltr"><<a href="mailto:aa@google.com">aa@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="it">On Mon, Jul 6, 2009 at 1:28 PM, Jonas Sicking<jonas@sicking.cc> wrote:<br>
</div><div><div></div><div class="ib">> On Mon, Jul 6, 2009 at 11:46 AM, Aaron Whyte<<a href="mailto:awhyte@google.com">awhyte@google.com</a>> wrote:<br>
>> When a page is loaded from an AppCache, even when online, external resources<br>
>> such as images will not be loaded at all.<br>
>> If <a href="http://foo.com" target="_blank">foo.com</a> has an image <img src="<a href="http://bar.com/img.png" target="_blank">http://bar.com/img.png</a>" />, then according<br>
>> to the steps in<br>
>> <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/offline.html#changesToNetworkingModel" target="_blank">http://www.whatwg.org/specs/web-apps/current-work/multipage/offline.html#changesToNetworkingModel</a><br>
>> it will fail the load for the resource.<br>
>> For example, someone with an Offline Gmail client would never be able to see<br>
>> cross-domain images in emails, even when completely online.<br>
>> There's no workaround in the current spec.<br>
><br>
> The workaround is for the gmail to download the images to gmails<br>
> servers and then serve them from a google domain. Not as simple as<br>
> simply being able to cache urls from other servers I agree, but doing<br>
> multi domain application caches is very complicated from a security<br>
> point of view so I think we wanted to stay clear of it for the first<br>
> iteration of the spec.<br>
<br>
</div></div>The spec already provides for loading resources not in the app cache<br>
from the network (across origins or not). It simply defaults to not<br>
allowing it. You have to opt-into the url prefixes you want to load<br>
from the network.<br>
<br>
I think we could fix this issue by simply changing the rules to<br>
default to allowing requests, and having the author mark the url<br>
prefixes he wants to blacklist from being loaded from the network.</blockquote><div><br></div><div>That would work too. We'd have to introduce a new kind of 'namespace' in the manifest file.</div></div>