18210 2008-03-29 12:56:39 -0700 DOMParser reports parsing errors differently than 2019-02-06 09:03:43 -0800 1 1 1 Unclassified WebKit DOM 528+ (Nightly build) PC Windows XP RESOLVED DUPLICATE 13057 P2 Normal --- 0 webkit webkit-unassigned ap cdumez oldest_to_newest 75784 0 webkit 2008-03-29 12:56:39 -0700 The DOMParser object doesn't report parsing errors. The following will cause a parser error in both Firefox and Opera: var xmldom = (new DOMParser()).parseFromString("<xml>", "text/xml"); The returned value is a document whose document element is <parseerror/> in Firefox and Opera; in WebKit it is <xml/> and no error occurs. 76046 1 ap 2008-04-01 00:29:58 -0700 I cannot reproduce this. Try entering the following into the address bar: javascript:alert((new XMLSerializer).serializeToString((new DOMParser()).parseFromString("<xml>", "text/xml"))) 76437 2 webkit 2008-04-06 12:39:14 -0700 Perhaps my original subject was incorrect. In Opera and FF, the <parsererror> element is the document element. In WebKit, it's inserted at the point of the parser error. This seems like a bug that should be fixed for interoperability. 76460 3 ap 2008-04-06 23:56:37 -0700 *** This bug has been marked as a duplicate of 13057 *** 1503024 4 lforschler 2019-02-06 09:03:43 -0800 Mass moving XML DOM bugs to the "DOM" Component.