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

Someone wanna help with this one? https://github.com/WebReflection/document-register-element/issues/142

I remember when this call about custom elements and `class`es was made. I willing to deal with it. I figured, the spec authors know what they're doing. It won't be a problem.

But it is a problem. It was a problem when y'all did it, it's still a problem today, and as far as I can tell the end is **not** in sight. 

Every non-toy implementation I've attempted to do with custom elements has been blocked by some variation of an issue stemming from the fact that custom elements are supposed to use a `class`.



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