- From: Jeff Burtoft <notifications@github.com>
- Date: Fri, 15 May 2015 20:39:46 -0700
- To: w3c/manifest <manifest@noreply.github.com>
Received on Saturday, 16 May 2015 03:40:13 UTC
I like having control over window.open in an app scenario. As an app you could want a different experience than on the web. Let me throw another example at you for scope. I use to work for a bank doing front end development. We had a few services that we integrate to for our bank customers. Things liked credit check, bill pay and redeeming points. These were what we called branded experiences, where the site looked like our site (we provided the template) and we passed them a token for auth, but the experience was on their dominion. Most of the time it was something like this: www.mybank.com --> mybank.outhersite.com --> www.mybank.com This type of shared experience wouldn't work within the current approach to scope. I could see this being common not just for auth but things like this shared experience, or even transactions that use external services like paypal or the like. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/380#issuecomment-102568199
Received on Saturday, 16 May 2015 03:40:13 UTC