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

> Installed app (in app navigation within scope)

Looks fine. (Terminology nit: Remains "standalone" without browser chrome, not "fullscreen").

> Browser navigation
...
> 6. As foo.com/app is in scope of an installed web app (Foo!), browser MAY indicate that Foo! is already installed and the user can switch to Foo app:

I would actually go further than this and say that the user agent MAY just automatically switch to the app and carry out the navigation there, rather than prompting the user. Once an app is installed, it is registered as managing that part of the web, and should always do so. But that should probably be left down to the implementation.

> 9. foo.com/form.html detects that it's about to unload. Alerts users that they could lose work.

If an app can only have one application context, this would be the only option. If an app could have multiple application contexts, the user agent could instead create an additional application context for the app to navigate to foo.com/app/whatever.html without having to unload foo.com/form.html.

> Installed app (following links outside scope)

Looks fine.

> Installed app (opening windows)
...
> 4. Overlay browser is shown. bbc.co.uk/news/some_story is shown. 

I think that by default this should open in a new browsing context in the browser, not an overlay window on top of the app, because it is out of scope of the app. There may be cases where the app author wants to opt-in to staying inside the app, for that I suggest something like using a "dialog" feature of window.open().

> Jumping between Bar and Foo

Looks fine.

> Identity is still problematic. There can be a third app that can subsume Foo!'s scope and start URL.
Need to deal with that in a separate bug.

I think two apps shouldn't be allowed to have overlapping scope. This could be done by either by the user agent refusing to install an app with a scope which overlaps that of another installed app, or alternatively by using the "last registration wins" approach taken by Service Worker scope.

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