Re: [whatwg/dom] No way to resolve a Promise with a cross domain WindowProxy (#536) from Shiino Yuki on 2017-11-17 (public-webapps-github@w3.org from November 2017)

From: Shiino Yuki <notifications@github.com>
Date: Fri, 17 Nov 2017 13:31:01 +0000 (UTC)
To: whatwg/dom <dom@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/dom/issues/536/345244266@github.com>

Blink's implementation is still far from the ideal state, but I can implement something so that `crossOriginWindow.then` returns `undefined`.  However, I have a concern.

If we add `then` to [HTML 7.2.3.3 CrossOriginGetOwnPropertyHelper](https://html.spec.whatwg.org/multipage/browsers.html#crossorigingetownpropertyhelper-(-o,-p-)), then `then` has a priority over [7.2.3.1 CrossOriginProperties](https://html.spec.whatwg.org/multipage/browsers.html#crossoriginproperties-(-o-)), right?  IIUC, it shadows a child browsing context with the name "then".

Should we deprioritize `then`?  `@@toStringTag`, etc. are probably okay because they're symbols.

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

Received on Friday, 17 November 2017 13:31:49 UTC