[w3c/manifest] Relationship between nestedly scoped web app manifests? (#539)

There is an explicit section [match-service-worker-registration](https://w3c.github.io/ServiceWorker/#match-service-worker-registration) declaring how nestedly scoped service workers work, where a SW with longest scope_url would "override"(bypass) all the others.

But of web app manifest, how nestedly scoped web app (manifest) effect with each other? Taking `/` and `/sub-app/` as an example, is the one with shorter path (which has a wider scope) totally bypassed? OR the longer-path one (the sub one) can inherit all missing members from the shorter/parent one? There seems no definition exist about this scenarios in the current spec.

Furthermore, there might exist some scenarios that a `/sub-app/` want treat `/` as sort of "parent app", where the sub-app can be navigated to from the "parent app" (in current browsing context) but has its own needs for a separated manifest (e.g. different themes/bg colors, different orientation, different desceiption etc. I think It's common?), thus should allow the navigation back from sub-app to "parent app".

There might be more complicated scenarios in practice, I believed It's worth discussion ;)   


-- 
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/539