Re: [manifest] Allow multiple application contexts per app (#294)

> It's not artificial until we find valid use cases (and use cases that are not covered by window.open). That's not to say there are no good use cases - but we should find those first and see who actually needs this (particularly people who are limited by window.open) ... and then, and only then, think about adding something like this.

Fair enough. So to confirm, as the spec is currently written calling window.open() from an application context will always create a browsing context without the manifest applied? The only way to create an application context with the manifest applied is by launching an app?

Just for refrerence, here is the algorithm from Jonas' original application scopes proposal, which I agree with:

>When opening a new context:
>1. If the new context is a "dialog" context, create a new dialog
>window and open the URL there.
>2. If the "target" of the navigation is "_blank" and the URL is not
>part of the current context's Apps' "scope", go to step 4.
>3. If the URL is part of the current context's App's "scope" or
>"open-in-app", open the new page within the current app.
>4. If the URL is part of multiple other App's "scope", show an
>application picker to the user and allow the user to choose which of
>the two applications to use.
>5. If the URL is part of another App's "scope", open the new page
>within that App.
>6. Open the URL in the system browser.
https://groups.google.com/forum/#!topic/mozilla.dev.b2g/Ufrz9UW-Z28

The reason I think this is important is to allow multiple pages of an app to be open at the same time, with the manifest applied. This becomes particularly important if we add capturing scope to the spec such that an app can capture navigations from a browsing context outside the app. Otherwise any navigation to a URL inside the scope of an app would always navigate the single application context for that app, potentially navigating the user away from a page they are still using.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/294#issuecomment-69334813