diff --git a/source b/source
index ec9157348bb..f8aa5389980 100644
--- a/source
+++ b/source
@@ -10579,6 +10579,8 @@ typedef (HTMLScriptElement or SVGScriptElement) LegacyOverrideBuiltIns]
partial interface Document {
+ static The Note that Document
parseHTMLUnsafe(DOMString html);
+
// resource metadata management
[PutForwards=href, LegacyUnforgeable] readonly attribute Location? location;
attribute USVString domain;
@@ -109055,6 +109057,8 @@ document.body.appendChild(frame)
also live here? -->
DOM parsing
+ The
+
DOMParser
interfaceDOMParser
interface allows authors to create new Document
objects
by parsing strings, as either HTML or XML.script
elements are not evaluated during parsing, and the resulting
document's encoding will always be
- UTF-8.
Values other than the above for type will cause a TypeError
exception
to be thrown.
The design of DOMParser
, as a class that needs to be constructed and
- then have its parseFromString()
method called,
- is an unfortunate historical artifact. If we were designing this functionality today it would be a
- standalone function.
parseFromString()
method
+ called, is an unfortunate historical artifact. If we were designing this functionality today it
+ would be a standalone function. For parsing HTML, the modern alternative is Document.parseHTMLUnsafe()
.
[Exposed=Window]
interface DOMParser {
@@ -109115,7 +109121,7 @@ enum DOMParserSupportedType {
Let document be a new Document
, whose content type is type and url is this's relevant global object's URL is this's relevant global object's associated Document
's URL.