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

hemuio left a comment (w3c/manifest#1180)

i read that, from where i find path scoped if given precedence over origin/host/domain, then would be convenient for developers to host pwa on same origin with path differences and functions align accordingly, and also could be better user experience 

For example, in browser(chrome/firefox) a web version pwa opened that is path scoped and installed on device, currently browser pick origin pwa installed not path scoped even if its installed, as it is directly mapping scope thus should be given priority over resolution which pwa to pick open that page

or could forget the path(complicating too much) and just explicit scoping should be enough for determination, if origin or path, pick just as stated in manifest

what do you mean by the longest scope given precedence? by character length? how longest determined, on what parameters?


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

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