Re: [w3c/webcomponents] Custom Element - untrackable upgrade (#671)

No, `customElements.whenDefined(tp.content.lastChild).catch(console.error);` would never resolve or reject or throw because `af-ter` is a valid custom element for which its definition might come in later asynchronously.

I'm suggesting that if you passing a div element, an element without `-`, etc... that can't possibly a custom element, we would return a rejected promise.

-- 
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/671#issuecomment-333264761