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

I think the idea was that the "processing of the manifest" could be separated, not necessarily things like icon fetches, as this would allow entities like crawlers or stores to be able to process the manifest in a spec-conformant way (so that devs can expect this).

I think the main sticking point here for me is the verification of the document_url origin and the start_url origin matching. Based on the pull request by @mgiuca, this would still be done for user agents as they would always pass in document_url, and the processing would then consider it. But a crawler might not have a document, for example.

Going further in the store / indexing / crawler direction, I would imagine that there would be suggestions in the spec about 'verifying start_url' by fetching it to look for a manifest link back to the current manifest being parsed.

Anyways, just some thoughts here. 🤷 

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