Re: [w3ctag/design-reviews] Service Worker Scope Pattern Matching explainer (#417)

I think one of the things we need to talk about here is multiple specs that have different concepts of scope, and different way to express scope.

I'm particularly concerned about the scope expression in service workers and the scope of web app manifests.  That comes up in two cases:
* ability to make declarative equivalents (in app manifests) of script features (in service workers), or vice-versa, and
* decisions about whether a feature belongs more in an app manifest or a service worker being biased by the scope-choosing needs of the feature's users rather than more fundamental aspects of which one is the right place for the feature.

It seems if app manifests and service workers have the same capabilities for expressing scopes, we'd avoid these problems.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/417#issuecomment-532943355