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

@trusktr this kind of workaround must not exist in a standard, it's too messy. Also forcing the developers to use only es6 classes will throw a lot of potential web-components adopters to other technologies and frameworks, turning the main objective of web components not reachable...

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

Received on Thursday, 30 March 2017 14:19:14 UTC