Don't set custom element state redundantly

As of whatwg/html#1309, this is no longer necessary, as it is taken care of in the Construct(C) step.
whatwg · May 24, 2016 · 0df362a · 0df362a
1 parent 1bb85a4
commit 0df362a
Show file tree

Hide file tree

Showing 2 changed files with 47 additions and 49 deletions.
diff --git a/dom.bs b/dom.bs
@@ -5722,8 +5722,6 @@ given a <var>document</var>, <var>localName</var>, <var>namespace</var>, and opt
      <var>localName</var>, then <a>throw</a> a {{NotSupportedError}}.
 
      <li><p>Set <var>result</var>'s <a for=Element>namespace prefix</a> to <var>prefix</var>.
-
-     <li><p>Set <var>result</var>'s <a>custom element state</a> to "<code>custom</code>".
     </ol>
    </li>
-Original file line number
+Diff line change
@@ Expand Up @@
          <var>localName</var>, then <a>throw</a> a {{NotSupportedError}}.
          <li><p>Set <var>result</var>'s <a for=Element>namespace prefix</a> to <var>prefix</var>.
-         <li><p>Set <var>result</var>'s <a>custom element state</a> to "<code>custom</code>".
         </ol>
        </li>
@@ Expand Down @@