Use URLPattern for scope member

[dmurph]

The new URLPattern feature would be a great match for the scope member in the manifest.

Does anyone need scope to be more expressive / flexible? Please put your use cases here :)

[wanderview]

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?

[dmurph]

I believe that we would be able to support nested scopes if the scope member was improved to be more flexible - I think a more accurate statement would be "we don't support overlapping scopes", and URLPattern allows developers to be able to, say, have path nested scopes without the scopes overlapping.

[wanderview]

Ah, ok. Although it may be difficult to tell if two URLPattern scopes are overlapping or not.

[LuHuangMSFT]

More cases that URLPattern could help with:

1. Scope that comprises multiple non-overlapping paths
   • Eg.: scope = contoso.com/a + contoso.com/b
2. Scope with wildcard path elements (eg. part of the URL path is a username that cannot be determined statically)
   • Eg.: scope = contoso.com/user/*/app
3. Being able to exclude files/paths from a scope
   • Eg.: scope = contoso.com/ - contoso.com/about - contoso.com/contact

[jcayzac]

At Rakuten we would certainly like this feature. Our current super app has to complement scope with a set of extra urls and exclude patterns, for each PWA. Standardization in the web manifest would make things easier for us.