Re: [whatwg/dom] Add "precustomized" custom element state (#894)

@annevk commented on this pull request.

Thanks, this looks good. And I guess also suggests we need a test for defined.

>  
 <p class=note>Whether or not an element is <a for=Element>defined</a> is used to determine the
 behavior of the '':defined'' pseudo-class. Whether or not an element is <a for=Element>custom</a> is
 used to determine the behavior of the <a href=#mutation-algorithms>mutation algorithms</a>. The
-"<code>failed</code>" state is used to ensure that if a <a>custom element constructor</a> fails to
-execute correctly the first time, it is not executed again by an
-<a lt="upgrade an element">upgrade</a>.</p>
+"<code>failed</code>" and "<code>precustomized</code>" states are used to ensure that if a <a>custom

No newlines in inline elements. Sorry that this is different from HTML.

>  
 <p class=note>Whether or not an element is <a for=Element>defined</a> is used to determine the
 behavior of the '':defined'' pseudo-class. Whether or not an element is <a for=Element>custom</a> is
 used to determine the behavior of the <a href=#mutation-algorithms>mutation algorithms</a>. The
-"<code>failed</code>" state is used to ensure that if a <a>custom element constructor</a> fails to
-execute correctly the first time, it is not executed again by an
-<a lt="upgrade an element">upgrade</a>.</p>
+"<code>failed</code>" and "<code>precustomized</code>" states are used to ensure that if a <a>custom
+element constructor</a> fails to execute correctly the first time, it is not executed again by an <a

Same.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/pull/894#pullrequestreview-490515542