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

I want to re-open this as it's come up internally (at Google). I wrote a doc explaining the rationale, the proposed change, and potential issues. It's quite messy at the moment though including a bunch of unrelated changes but I wanted to restart this conversation.

https://docs.google.com/document/d/1NUsoTWkWrPFFNnxR00r1NF-MXzq-_rjl2ldAhZm-TEw/edit

I will follow up with a less messy proposal after a bit of informal discussion. (I'm also not 100% convinced that we should do this any more after @philloooo pointed out that from a security perspective, we don't necessarily want manifests to be able to "appify" a site on another origin without that site linking back to the manifest. But if we decide not to do this on those grounds, we can properly document that as I don't think this objection has been raised before.)

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

Message ID: <w3c/manifest/issues/668/1386542951@github.com>