Re: [slightlyoff/ServiceWorker] Eliminate usage of entry and incumbent settings objects (#922)

I'd need to check them thoroughly but presume many of them actually implemented entry and incumbent. I changed `navigator.serviceWorker.register(url)` and `navigator.serviceWorker.getRegistration(url)` to use entry for parsing url at least.

For that change, I was referencing the example code in https://www.w3.org/TR/2016/WD-html51-20160503/webappapis.html#calling-scripts section the corresponding part of which in WHATWG version is now replaced with your recent patches that clarify those concepts.

Having tried the example code with `location.assign()`, it turned out Chrome and IE (didn't try with Edge yet) use entry for parsing the url and Firefox uses current. (I saw you filed the `Location` object behavior in https://github.com/whatwg/html/issues/1431)

To sort them out in SW spec, I'd want to check once again if the goal is to make them all use current instead of entry and incumbent for both parsing urls and security checks? And don't we need any implementer/developer feedback on the behavior change? (I agree we should sort them out sooner than later but somewhat worry about the impact.)

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/922#issuecomment-229573064