Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)

> What you're missing is return el; in the constructor.

I don't think so, because I'm implicitly returning `this` which has the correct prototype (`el`) in it.

It'd be great if `Custom Elements v2` doesn't have this issue, and is not restricted to a subset of JavaScript in terms of how we define classes.

If plain regular ES5 classes can work perfectly with the polyfilled version of `Custom Elements v1`, then surely it is possible to make the native version work too.

-- 
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/587#issuecomment-381382562