Re: [webcomponents] Define the behavior when a custom element constructor returns an element with a parent node. (#412)

So, what is the conclusion here, in terms of modifications to the current spec? That is, given the two synchronous-construction cases:

- createElement(NS)
- the parser

and the following possible things that could go wrong:

- wrong prefix
- wrong localName
- wrong namespace
- has attributes
- has a parent
- has children

What additional checks do we insert, in which cases?

Or do we just insert a non-normative note (in the "create an element" algorithm's "If synchronous custom elements flag is set" section) saying that the returned element may have some of these things having gone wrong?

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/412#issuecomment-193935169

Received on Tuesday, 8 March 2016 19:34:37 UTC