Re: [w3c/manifest] Processing the manifest is no longer a function of document URL (#834)

> If the manifest has no scope (i.e. because it has no start_url), the manifest processor deletes all scope-dependent members.

Wait, I just realised, this already happens automatically, due to the change to "within scope" to always return false if scope is undefined.

So we don't need to worry about the case where the manifest has an invalid scope. The only case we need to explicitly invalidate these members is the #784 case: if you link to a manifest from a document whose origin does not match the manifest's valid scope.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/pull/834#issuecomment-654079275