W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2016

[Bug 18547] Make all IDL methods have [ImplicitThis] behavior, and then get rid of [ImplicitThis]

From: <bugzilla@jessica.w3.org>
Date: Mon, 08 Feb 2016 19:33:23 +0000
To: public-script-coord@w3.org
Message-ID: <bug-18547-3890-M89IO5adNg@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18547

Domenic Denicola <d@domenic.me> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |d@domenic.me
            Summary|Add [ImplicitThis] to       |Make all IDL methods have
                   |EventTarget?                |[ImplicitThis] behavior,
                   |                            |and then get rid of
                   |                            |[ImplicitThis]

--- Comment #9 from Domenic Denicola <d@domenic.me> ---
Per the thread starting at
https://lists.w3.org/Archives/Public/public-script-coord/2015JanMar/0109.html,
and concluding around
https://lists.w3.org/Archives/Public/public-script-coord/2015JanMar/0122.html,
we decided on an alternate plan, which I've now updated the title of the bug to
reflect:

- All IDL-defined methods should have the [ImplicitThis]-like behavior, where
if `this` is undefined, it becomes the global of the realm of the function
involved. (Or, the corresponding WindowProxy? ugh).

- This will cause brand check failures immediately when doing things like
`Node.prototype.insertBefore.call(undefined, ...)` since a Window is not a
Node. So this is good; a TypeError will be thrown as expected.

- Once this is done we can remove [ImplicitThis] from everywhere.

See also https://github.com/whatwg/html/issues/643.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 8 February 2016 19:33:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:24 UTC