- From: Rob Dolin (MSFT) <notifications@github.com>
- Date: Thu, 07 Apr 2016 15:17:45 -0700
- To: w3c/manifest <manifest@noreply.github.com>
Received on Thursday, 7 April 2016 22:18:12 UTC
There are some cases where a web app could have multiple scopes. * In one case, a web app (scope:Example.com) might have a CDN (scope:ExampleCDN.com), personal data (scope:MyExample.com), etc. that is served from a second domain. * In another case, a web app (scope:Chat.Example.com) might have peer subdomains that are in-scope (scope:Music.Example.com and scope:Video.Example.com) but might also have peer domains that are out-of-scope (scope:Events.Example.com) PROPOSAL: Add an “additional_scopes” array element for web app developers to optionally specify additional scopes FAQ: Q: Why not replace the current scope object with a scopes array? A: We do not want to break backwards compatibility with implemented manifests that use scope Q: What might this look like? A: ` "scope": ... , ` ` "additional_scopes": [ ... ], ` --- 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/449
Received on Thursday, 7 April 2016 22:18:12 UTC