Re: [w3c/webcomponents] Can't reuse custom element constructors? (#618)

This is why we proposed to make the first argument of each constructor the local name but since we’re not doing that in v1 API, this would indeed becomes an issue.

In the prototype I implemented, I made this constructor argument optional so that if a constructor defined exactly one custom element, it would be omitted.  We could go on that route still since that would be backwards compatible.

-- 
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/618#issuecomment-268120552

Received on Tuesday, 20 December 2016 00:39:48 UTC