Re: [heycam/webidl] Is a subclass still a platform object? (#540)

Oh, also, even in today's spec https://heycam.github.io/webidl/#interface-object creation steps step 11 asserts that the newly-created thing's Realm is the realm of the constructor, not of the NewTarget.  Which is an assert Chrome would fail.

Looks like that assert is not clearly supported by any normative requirements, though.  Those normative requirements used to exist, but were removed in <https://github.com/heycam/webidl/commit/4a8f57e2> for some reason.  Before that, there were clear statements like:

> This object also must be associated with the ECMAScript global environment associated with the [=named constructor=]

which seem to be gone now.  @tobie, @domenic, why did those get removed?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/issues/540#issuecomment-379016514