Re: [w3c/webcomponents] ES5 consideration for custom elements (#423)

@trusktr this is exactly what's happening. This thread is only about purely ES5 style constructors which call their super constructor with Function.call. In this case `new.target` won't be set. 

I think this is mainly a concern for output of compilers and code that aims to be compatible with both native implementations and polyfills on browsers without `new.target`. I wouldn't worry too much though, it's possible to make a small shim that overrides HTMLElement and sets `new.target` to `this.constructor`, which is usually set to the right function in ES5 inheritance patterns.

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