- From: Ryosuke Niwa <notifications@github.com>
- Date: Tue, 22 Mar 2016 16:32:49 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Tuesday, 22 March 2016 23:33:19 UTC
The spec doesn't imply either. `super()` is basically a syntactic sugar of `Reflect.construct`. > `Reflect.construct` will not be required in the future as a non-exotic object will be returned from the `HTMLElement` constructor This is certainly not the case. `HTMLElement` constructor will continue to return an exotic object for the foreseeable future. > Is this implying that browsers do not currently have Reflect.construct, but in the future browsers could invoke the base constructor through either a call to super() or using Reflect.construct? All browsers that do support custom elements will support `Reflect.construct`. Perhaps the spec could be updated to also mention `Reflect.construct` for clarity. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/423#issuecomment-200079122
Received on Tuesday, 22 March 2016 23:33:19 UTC