[ServiceWorker] should scope matching do substring comparison within a path element? (#734)

Currently step 3 of [scope matching][https://slightlyoff.github.io/ServiceWorker/spec/service_worker/index.html#scope-match-algorithm] is:

> Let matchingScope be the longest [[key]] in scope to registration map starting with the value of clientURLString.

Currently this wording means that '/some/scope' would match '/some/scopeislong'.  These two scopes represent peers in the sites tree structure.

It seems very surprising that these two match because it prevents you from having separate service workers for separate parts of your tree simply due to one being a substring of the other.

---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/734