DOMParser.parseFromString() should support creating HTML Document with mimetype text/html

Source/core/xml/DOMParser.cpp

Index: Source/core/xml/DOMParser.cpp
diff --git a/Source/core/xml/DOMParser.cpp b/Source/core/xml/DOMParser.cpp
index b923b46ec23902e17faae02d2457a0238f28e989..475eb975f097e9309fa3c1757ab4409c43474fdd 100644
--- a/Source/core/xml/DOMParser.cpp
+++ b/Source/core/xml/DOMParser.cpp
@@ -27,7 +27,7 @@ namespace WebCore {
 
 PassRefPtr<Document> DOMParser::parseFromString(const String& str, const String& contentType)
 {
-    if (!DOMImplementation::isXMLMIMEType(contentType))
+    if (!(DOMImplementation::isXMLMIMEType(contentType) || contentType == "text/html"))

[abarth-chromium, 2013/09/05 17:25:31]

Can you distribute the ! inside the || ?  I think that will make this line of
code read better:

if (!DOMImplementation::isXMLMIMEType(contentType) && contentType !=
"text/html")
..

[eseidel, 2013/09/05 17:26:28]

I'm concerned that we support more mime types than the spec allows us to.

I would like us to see a test of what mimetypes we support and what happens when
we don't support them. It's OK for such a test to document (with FAIL) our
current spec-divergent behavior, but I'd like to see it tested.

         return 0;
 
     RefPtr<Document> doc = DOMImplementation::createDocument(contentType, 0, KURL(), false);