Re: [w3c/ServiceWorker] Consider deprecating the ability for scope to match query parameters (#1469)

The scope is a prefix, so it seems pretty obvious that order of things in the query string matters.

I don't think we can just add pattern matching to regular scope strings (and other places we use URLs). `*` crops up in most patterns, and it's also valid in a URL.

If someone deliberately puts `?foo` in a scope string, it seems weird to just ignore it. Shouldn't it do something, or throw?

-- 
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/1469#issuecomment-531549522