Re: [whatwg/dom] No way to resolve a Promise with a cross domain WindowProxy (#536)

> then then has a priority over 7.2.3.1 CrossOriginProperties, right? IIUC, it shadows a child browsing context with the name "then".

Oh, good catch.  I got confused between undefined-the-value and undefined-the-descriptor when looking at https://html.spec.whatwg.org/multipage/window-object.html#windowproxy-getownproperty

I agree that this is not desirable.  If there's a named subframe called "then", we should expose it in the usual way.  It won't affect the Promise behavior, per https://github.com/whatwg/dom/issues/536#issuecomment-344624827

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/536#issuecomment-345277084