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

Having a think about this... will respond soon... thinking out loud here, I'm a bit uncomfortable with tying insatiability to processing (and I'm even leaning towards treating the whole idea of "installabilty" as a non-normative concept - but need to think about this more). 

I feel like insatiability is more of an implementation detail/decision, and not a core concern of the processed manifest: i.e., a user agent should be able to pick up a [=processed manifest=] and make a determination about its installability based on the values if it wants, but it should be free to do whatever it wants with the manifest itself. 

It's the user that makes the determination to install something. The user agent (and this spec) just takes actions through processing to make sure installing something using a manifest is a safe as possible. 

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