Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)

> 1.) An extension for controlled scopes that marks them as "pathComponent" matches to solve the `/` issue. This might be an option to registrations.
> 2.) An extension that marks scopes as "exact"; not matching `/foo/*` when you only mean to handle `/foo`. How this and the first intersect is an interesting question.

I don't understand the difference between "pathComponent" and "exact" in these two (alternative?) proposals? Seems like they both do the same thing which is "/foo" (without a slash) would only handle "/foo" and "/foo/anything" but not "/foobar".

Having it be opt-in is fine, though it adds to the complexity of correctly setting up a service worker. I'd ask that we try to find a solution that has an analogue in Web App Manifest as well, since this issue [also affects Manifest](https://github.com/w3c/manifest/issues/554).

@wanderview:
> should we consider suborigins instead of expanding scope?

Do you mean force developers to migrate their app to a sub-origin rather than a path?
 I addressed this [here](https://github.com/w3c/ServiceWorker/issues/1272#issuecomment-364280626); I don't think it's going to help adoption if we force developers to migrate their entire site to a new URL. Effectively, we shut off a bunch of existing sites from adopting SW (and, by extension, Manifest).

-- 
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/1272#issuecomment-364326241