Re: [w3c/ServiceWorker] scope pattern matching (#1468)

I'm not sure what you mean by "very much focused on paths".  You can set values/patterns for scheme, hostname, etc.  Indeed, service worker scope patterns must have a non-variable value set for all parts of the origin.

In addition, it seems supporting relative behavior is important?  If we don't support that then it becomes very difficult to build a site that can be hosted in different locations without requiring modifications.  Supporting relative behavior seems like a core feature of the web and I'm hesitant to drop it.  (Its also supported by legacy SW scopes, so would be a backward compat issue.)

The baseURL concept seemed like a natural fit for these things to me, but happy to discuss alternative API shapes.

-- 
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/ServiceWorker/issues/1468#issuecomment-689615737