Re: [webcomponents] s/document.registerElement/document.defineElement and no return value (#400)

I don't think we should do this until we also implement the changed semantics (which are pretty pervasive) regarding element constructors and the HTMLElement constructor, discussed recently on public-webapps. Otherwise it gives a false impression that the consensus API is ready for implementation. It's better to keep the document in the old state until the new one is ready.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/pull/400#issuecomment-189340399