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

The reason I'm having this problem is because I'm writing classes that I can use with Custom Elements v1 using `constructor`s, but I need to support older browsers that don't have `Reflect.construct`, so I'm writing classes that work when registered with `v0` or `v1` (this seems like a reasonable thing for a Custom Element library author to want).

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