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

I've verified by code inspection that Chrome and Firefox seem to agree on the various places that this spec and fetch use "entry", documented in https://github.com/whatwg/html/issues/1431. Most of them are around URL parsing.

I think it would be ideal if implementers were willing to coordinate on a switch to the relevant settings object of the object on which the method is being called (or the current settings object in the case of constructors). This might require use counters if people think this change is risky; it seems very unlikely to be risky to me given how few developers do these sort of multi-global things, but maybe it's better to be safe than sorry. /cc @wanderview @mattto 

What would be a good next step here? Would writing up a spec PR with the changes I propose be a good way to concretize this?

---
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-231633479