[w3c/manifest] multiple pwa on same origin could be conflicting for app scoped to path (Issue #1180)

hemuio created an issue (w3c/manifest#1180)

multiple pwa on same origin with different path could be conflicting, at how pwa over path app opens and their installations by browsers

where origin/home is taken implicitly host of other as usually scoped in such manner, and how browser behave, that may not be the case intended, and pwas that are taken as sub of host may have their seperate existence and scope to themselves first

these issues could be resolved through path ones ((origin)/(path)) given higher precedence over origin/host if scope is declared 
or new manifest key that explicit it somehow, determined how browser behave to each by declaration, as there is already "scope" key then precedence would resolve, yet there could be more where new key would be suiting.
then atleast those path scoped pwa will open in their own window/pwa session then in host, even if origin scoped app installed

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/1180
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/issues/1180@github.com>