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

@nnmrts you can use the V0 poly described [in here](https://medium.com/@WebReflection/a-custom-elements-v0-grampafill-dc1319420e9b), or use the [polyfill](https://github.com/WebReflection/document-register-element) that Google AMP sponsored and used since the beginning to bring Custom Elements everywhere years ago (plus AFrame, StencilJS, etctera).

Once you have basics portable, you can easily create that `newh` thing you want.

Yet the direction of W3C should be to promote modern standards, not just old conventions for libraries authors. We have too many libraries already and all we need is better, and wider support, of native features.

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

Received on Wednesday, 28 February 2018 00:30:16 UTC