Re: [heycam/webidl] Add an algorithm to create a platform object. (#635)

littledan commented on this pull request.



>  
     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)?
+        1.  Let |newTargetPrototype| be [=?=] [$Get$](|newTarget|, "prototype").

To clarify, WebKit basically doesn't support subclassing URL even in the narrow `new.target` sense (ignoring the edge-casey fallback behavior):

```js
> class MyUrl extends URL { }
< undefined
> new MyUrl("file:///foo").constructor
< function URL() {
    [native code]
}
```

Choosing one and writing tests will be a big help! But we do have 2/3 already supporting subclassing URL, so I think we're pretty safe to standardize that part.

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