Make CustomElementConstructor exceptions more consistent

annevk · web-flow · commit b1b08e118676 · 2019-04-15T14:31:14.000+02:00
And allow for simplification of "create an element" by moving a step into IDL. Tests: web-platform-tests/wpt#16328. Corresponding DOM changes: whatwg/dom#751. Fixes whatwg#4520.
diff --git a/source b/source
@@ -66820,7 +66820,7 @@ interface <dfn>CustomElementRegistry</dfn> {
   [<span>CEReactions</span>] void <span data-x="dom-CustomElementRegistry-upgrade">upgrade</span>(<span>Node</span> root);
 };
 
-callback <dfn>CustomElementConstructor</dfn> = any ();
+callback <dfn>CustomElementConstructor</dfn> = <span>HTMLElement</span> ();
 
 dictionary <dfn>ElementDefinitionOptions</dfn> {
   DOMString extends;
@@ -67227,13 +67227,13 @@ customElements.define("x-foo", class extends HTMLElement {
      </li>
 
      <li>
-      <p>If <span>SameValue</span>(<var>constructResult</var>, <var>element</var>) is false,
-      then throw an <span>"<code>InvalidStateError</code>"</span> <code>DOMException</code>.</p>
+      <p>If <span>SameValue</span>(<var>constructResult</var>, <var>element</var>) is false, then
+      throw a <code>TypeError</code>.</p>
 
       <p class="note">This can occur if <var>C</var> constructs another instance of the same custom
       element before calling <code data-x="">super()</code>, or if <var>C</var> uses JavaScript's
-      <code data-x="">return</code>-override feature to return an arbitrary object from the
-      constructor.</p>
+      <code data-x="">return</code>-override feature to return an arbitrary <code>HTMLElement</code>
+      object from the constructor.</p>
      </li>
     </ol>
 
