Re: [w3c/manifest] Use URLPattern for scope member (#1002)

Note, one of the main use cases for making service worker scopes more flexible is to handle nested scope situations.  Product 1 is at "example.com/" and Product 2 is at "example.com/foo/".  The Product 1 team wanted to be able to restrict their scope to not automatically cover Product 2 in order to reduce the risk of breaking the other product.

My understanding is that installed PWAs don't support nested scopes.  Is that true?  Would it still be true if the scope member was improved to be more flexible?

-- 
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/1002#issuecomment-918368019