Re: [slightlyoff/ServiceWorker] Remove frameType, maybe add ancestorOrigins (#732)

@annevk, I'm planning to factor the steps of [`location.ancestorOrigins`](https://html.spec.whatwg.org/multipage/browsers.html#dom-location-ancestororigins) out as an algorithm that both `location.ancestorOrigins` and `WindowClient.ancestorOrigins` can invoke (taking an environment settings object as an argument.)

Currently, `location.ancestorOrigins`'s step 1 throws "SecurityError" if the relevant document's origin is not the same as entry settings object's origin. I don't think this would be meaningful for `WindowClient.ancestorOrigins` where the entry settings object's origin will always be the same as the client's origin. I'm not sure what the purpose of this security check in the first place.

In case we should retain this entry settings object checking step, should I make the algorithm take both relevant settings object and the entry settings object as arguments? Or any good idea how to define this algorithm?

/cc @domenic 

-- 
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/732#issuecomment-240658993