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

Aha, I know what the best solution is (thought it's not that good):

I can tell app developers: if you want to register my Custom Elements, you need to detect the user's browser, then use `document.registerElement` in IE/Edge/Firefox (with polyfill), otherwise you can likely use `customElements.define` in all the other browsers as long as they support `Reflect.construct`.

Now, that _uuugly_!

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