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

I'm revising this again, and, as the spec level, I just don't think it's possible to separate them right now.

That's not to say that auxiliary crawlers, app stores, and other software can't treat the manifest as independent (they can and should, and that's fine); but at a spec level (and for the purpose of conforming "user agents") the manifest is inherently tied to its client window and document for the reasons I mentioned above.  

Let's continue to stick to "browser land" for the purpose of conformance, as otherwise the scope of the problem becomes too large. 

We can continue to revise this after we at least standardize how the three existing engines handle web manifests.


-- 
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-895013042