- From: Matt Giuca <notifications@github.com>
- Date: Sun, 12 Jul 2020 18:05:30 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 13 July 2020 01:05:43 UTC
> On a somewhat related note: Does anyone think it might make sense to move `related_applications` to the App Info spec? `related_applications` is directly used by the in-incubation [`getInstalledRelatedApps`](https://github.com/WICG/get-installed-related-apps/) feature, which is implemented in browsers, not by other processors. Now, that's in incubation, but my point is that it's difficult for both new APIs to be designed or for browser manufacturers to make use of metadata if it's "not really part of the manifest, just supplemental information". Honestly, I wish we didn't split the manifest into App Info vs main. As I argued when it was proposed, I think it's an unhelpful distinction to say "these members are for browsers" vs "these members are for other manifest processors". What if a browser wants to use a member from App Info, for example if we wanted to start displaying screenshots in the browser at install time? -- 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/862#issuecomment-657307054
Received on Monday, 13 July 2020 01:05:43 UTC