Re: [w3c/manifest] Processing the manifest is no longer a function of document URL (#834) from Matt Giuca on 2020-07-03 (public-webapps-github@w3.org from July 2020)

From: Matt Giuca <notifications@github.com>
Date: Thu, 02 Jul 2020 22:37:44 -0700
To: w3c/manifest <manifest@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/manifest/pull/834/c653360463@github.com>

Yeah I just had a similar thought.

What if you have an app whose `start_url` and `scope` are valid, and has shortcuts, share targets, etc, within that scope. The manifest is fully legit. Then you link to that manifest from a document on a different origin. This would replace the `start_url` and `scope` with the document, but still allow you to install it. All of the shortcuts and share targets, etc, would remain valid, but no longer be on the same origin as `start_url` and `scope`.

I think we have to 🔥 the whole manifest. Actually I think this is the subject of #784.

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

Received on Friday, 3 July 2020 05:37:56 UTC