- From: Anne van Kesteren <notifications@github.com>
- Date: Fri, 08 Feb 2019 00:29:15 -0800
- To: heycam/webidl <webidl@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 8 February 2019 08:29:38 UTC
annevk commented on this pull request.
> @@ -12349,12 +12363,60 @@ It is the responsibility of specifications using Web IDL to state
which global environment (or, by proxy, which global object) each platform
object is associated with.
+<div algorithm>
+ To <dfn export lt="new|create|create a new|create an object implementing|create an object
+ implementing the interface">create an object implementing the interface</dfn> |interface| in the
+ Realm |realm|, with optional `new.target` value |newTarget|, perform the following steps:
+
+ 1. Assert: |interface| is [=exposed=] in |realm|.
+ 1. Let prototype be the [=interface prototype object=] for |interface| in
+ |realm|.
+ 1. If |newTarget| is provided, then:
+ 1. Issue: If we just pass {{NewTarget}} through in a constructor, would this not
+ always be defined (sometimes to the [=interface object=] itself)?
(I think even if we improved how to define a constructor, you still need new, e.g., for tear-off objects and such.)
--
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/pull/635#discussion_r254987052
Received on Friday, 8 February 2019 08:29:38 UTC