[whatwg] Foreign fallback appcache entries

Thu Sep 30 19:29:06 PDT 2010

"Foreign" means that the main resource has a different manifest than the one referencing it. E.g.

foo.manifest:
CACHE MANIFEST
iframe.html

iframe.html:
<html manifest="bar.manifest">
...

So, I don't think that the same origin requirement answers this. WebKit bug <https://bugs.webkit.org/show_bug.cgi?id=44406> has a live demo (Firefox 3.6.10 handles it correctly, according to my reading of the spec).

- WBR, Alexey Proskuryakov

30.09.2010, в 18:21, Michael Nordman написал(а):

> I don't think 'fallback' entries can be foreign because they must be
> of the same-origin as the manifest.
> 
> "Fallback namespaces and fallback entries must have the same origin as
> the manifest itself."
> 
> On Thu, Sep 30, 2010 at 4:38 PM, Alexey Proskuryakov <ap at webkit.org> wrote:
>> 
>> In definitions of application cache entry categories, it's mentioned that an explicit entry can also be marked as foreign. This contrasts with fallback entries, for which no such notice is made.
>> 
>> It still appears that the intention was for fallback entries to sometimes be foreign - in particular, section 6.5.1 says "Let candidate be the fallback resource" and then "If candidate is not marked as foreign..."
>> 
>> I found it confusing that there is a specific mention of foreign for explicit entries, but not for fallback ones.
>> 
>> - WBR, Alexey Proskuryakov
>> 
>> 