Re: [w3c/manifest] Manifest processing should not be a function of document URL (#668)

> So isn't this whole concept of seperation of document vs manifest simply impractical?

Mostly, yes. Because things like the content security policy, etc. are governed by the client settings object. This affects, at a minimum, how icons are loaded. But it also affects other defaults (the ones where the document URL is used as a fallback). 

On reflection, I think trying to decouple the manifest from the document might not work because they depend on each other too much... it be like decoupling a stylesheet from the documents the style sheet is applied to.    
  

-- 
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/issues/668#issuecomment-791189633