Re: [ServiceWorker] openWindow with a WebApp manifests (#720)

> Of course, this begs the question what should be done if the same site is opened as an installed app and in a normal browser window. Do you end up with two registrations? Are they effectively treated as separate origins? Thats what we do on firefox os, but its unclear to me if thats correct or desirable.

FWIW we're moving away from this behaviour. I think this maybe relates to deep linking [1] and scope [2]. My interpretation is that when a web app is installed, it should be registered as handling a URL scope specified by the scope property, then any navigation from an existing window or the creation of a new window at a URL within that navigation scope should have the metadata from the manifest applied. In other words, creating a new window within the navigation scope of an installed app should make the browsing context of that window an application context. This is why I think manifest scope is important as well as Service Worker scope.

This is purely theoretical at this point as to my knowledge nobody has implemented this yet. On Android I can see this potentially mapping onto App Links [3], but I'm not sure whether Google has any intention of implementing this part of the spec in Chrome?

1. http://www.w3.org/TR/appmanifest/#deep-links
2. http://www.w3.org/TR/appmanifest/#navigation-scope
3. https://developer.android.com/preview/features/app-linking.html

---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/720#issuecomment-124033371