Re: [w3c/webcomponents] Editorial: create an element's "new element" step (#463)

It seems reasonably doable. Would have to think about it a little bit, but if you know it's not the 4.1 substeps (through a conditional that seems like it can be created) and you make sure "element interface" returns HTMLElement to handle the 4.2 substeps case you can allocate an element early (and an otherwise statement to handle the constructor dance).

Then the following steps can handle details around is="" attributes and whether or not to queue something.

---
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/463#issuecomment-203015294