Re: [w3c/DOM-Parsing] Move DOMParser to HTML (#60)

sideshowbarker commented on this pull request.



> -
-    <dt><var>document</var> = <var>domparser</var> . <a data-link-for=DOMParser>parseFromString</a> ( <var>str</var>, <var>type</var> )
-    <dd>Parse <var>str</var> using a parser that matches <var>type</var>'s supported MIME types
-    (either XML or HTML), and return a <a>Document</a> object contained the parsed content if
-    successful. If not successful, returns a <a>Document</a> describing the error.
-    <dd>If <var>type</var> does not match a value in the <a>SupportedType</a> enumeration, an
-    exception is thrown [[WEBIDL]].
-  </dl>
+  <span id="dom-domparser"></span>
+  <span id="dom-domparser-parsefromstring"></span>
+  <span id="idl-def-supportedtype"></span>
+  <span id="dom-supportedtype-text/html"></span>
+  <span id="dom-supportedtype-text/xml"></span>
+  <span id="dom-supportedtype-application/xml"></span>
+  <span id="dom-supportedtype-application/xhtml+xml"></span>
+  <span id="dom-supportedtype-image/svg+xml"></span>

This mechanism for preserving the IDs is clever. We should do the same thing for any other cases where we’re moving something out of a spec, and maybe consider documenting it somewhere as a best practice (though I don’t know often this case comes up). Among other reasons, it ensures any existing links in the Specifications tables in MDN articles still bring readers to the point in the document where they need to be (in this, to the statement that the content’s been moved to the HTML spec).

-- 
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/DOM-Parsing/pull/60#pullrequestreview-349859241