47768 2010-10-16 07:30:48 -0700 XMLSerializer serializes BR as <BR> not <BR/> 2023-03-27 08:50:21 -0700 1 1 1 Unclassified WebKit XML 528+ (Nightly build) All All RESOLVED CONFIGURATION CHANGED P2 Major --- 0 dsr webkit-unassigned annevk ap cdumez christoph.burgmer peterx14 oldest_to_newest 295129 0 70953 dsr 2010-10-16 07:30:48 -0700 Created attachment 70953 Reproduce XML serialization error for HTML br element My browser is Chromium 6.0.472.62 (Developer Build 59676) Ubuntu 10.04, WebKit 534.3 V8 2.2.24.23. I am using XMLSerializer.serializeToString to serialize an HTML element and its content to XML. Unfortunately serializing content including a BR element then results in malformed XML. This is a nuisance when serializing markup to a server for download by other browsers, e.g. as part of a browser-based document editor. Other browsers e.g. Firefox get this right. Try viewing the attached HTML document in webkit, Opera and Firefox to see what I mean. 295177 1 ap 2010-10-16 17:17:06 -0700 That's more or less intentional behavior. WebKit makes the serialization form choice based on what is being serialized, not on what API happened to be used. See also: bug 16496. 295205 2 dsr 2010-10-17 02:41:34 -0700 If you want to get an HTML serialization, then you can use innerHTML, but the XML serialization should be XML for interoperability with other browsers. I did some more experiments and found that regardless of the namespace of the parent element, BR is only serialized by webkit as well formed XML if you set its namespace to be something other than "http://www.w3.org/1999/xhtml". Thus the webkit implementation seems to be examining the namespace for each element and switching its serialization on the fly with the end result that you can't get well formed XML if there were any empty elements in the "http://www.w3.org/1999/xhtml" namespace. 295251 3 70980 ap 2010-10-17 11:49:46 -0700 Created attachment 70980 XHTML test case > If you want to get an HTML serialization, then you can use innerHTML This is not accurate in XML documents per HTML5. See <http://www.whatwg.org/specs/web-apps/current-work/multipage/apis-in-html-documents.html#innerhtml>: ----------------------------- On getting, if the node's document is an HTML document, then the attribute must return the result of running the HTML fragment serialization algorithm on the node; otherwise, the node's document is an XML document, and the attribute must return the result of running the XML fragment serialization algorithm on the node instead (this might raise an exception instead of returning a string). ----------------------------- So, innerHTML changes its behavior depending on what's being serialized. > but the XML serialization should be XML for interoperability with other browsers. There is no dispute about that being a strong argument for adopting Firefox behavior. > I did some more experiments and found that regardless of the namespace of the parent element, > BR is only serialized by webkit as well formed XML if you set its namespace to be something other > than "http://www.w3.org/1999/xhtml". This is not what I'm seeing on the attached test case. 726176 4 peterx14 2012-09-22 14:27:12 -0700 My browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.10 (KHTML, like Gecko) Ubuntu/12.04 Chromium/23.0.1262.0 Chrome/23.0.1262.0 Safari/537.10 Example 1: HTML served as text/html http://clickindustrial.com/test/public/20120908/test01.html Example 2: XHTML served as text/html http://clickindustrial.com/test/public/20120908/test02.html Example 3: XHTML served as application/xhtml+xml http://clickindustrial.com/test/public/20120908/test02.xhtml Only example 3 outputs well-formed XML, which isn't what I'd expect an XMLSerializer to do! This is also inconsistent with Firefox and Opera: http://clickindustrial.com/test/public/20120908/test01.png ^ the above screenshots are based on Example 1 above. If a page is marked-up as HTML or is XHTML but served as text/html, there appears to be no way in WebKit to serialize it as XML, short of creating a new XML DOM, walking to HTML DOM and re-creating elements in the XML DOM. 726276 5 ap 2012-09-23 10:44:44 -0700 > Only example 3 outputs well-formed XML, which isn't what I'd expect an XMLSerializer to do! As mentioned in comments 1, this is not what WebKit implements - XMLSerializer just serializes the document without magically converting it to a different kind of a document. 726658 6 peterx14 2012-09-24 07:48:11 -0700 Just to clarify, my point is that I'd expect something called "XMLSerializer" to generate XML. If it does not do this, then it should surely be called just plain "Serializer". And therefore, being called XMLSerializer and not outputting XML must therefore be a bug? Additionally, I can't think-of/find a viable alternative or work-around (tree-walking, DOM copying is kind of slow!). For my use-case, I need well-formed XML in order to push it through an XSL transformation. Conversely, if XMLSerializer actually output XML, it would be trivial to convert XHTML to HTML using a simple XSL transformation. 726705 7 ap 2012-09-24 08:42:17 -0700 > I'd expect something called "XMLSerializer" to generate XML I see where you are coming from, but can't really subscribe to this line of thinking. XMLHttpRequest doesn't have much to do with XML either. XSLT has a lot of rough edges when used on the Web - in fact, you can't even produce <br> without violating the spec, see <https://www.w3.org/Bugs/Public/show_bug.cgi?id=18460>. 950578 8 christoph.burgmer 2013-11-14 02:51:58 -0800 As I was hit by the same limitation I sat down to implement a serializer in plain JS. I now hope that this can benefit others. You'll find a demo here: http://cburgmer.github.io/xmlserializer.js/. 1944255 9 annevk 2023-03-27 08:50:21 -0700 This appears to have been fixed at some point. 70953 2010-10-16 07:30:48 -0700 2010-10-16 07:30:48 -0700 Reproduce XML serialization error for HTML br element test.html text/html 961 dsr PGh0bWwgbGFuZz0iZW4tVVMiPgo8aGVhZD4KPHRpdGxlPlRlc3QgWE1MU2VyaWFsaXplcjwvdGl0 bGU+CjxzY3JpcHQgdHlwZT0idGV4dC9qYXZhc2NyaXB0Ij4Kd2luZG93LmFkZEV2ZW50TGlzdGVu ZXIoImxvYWQiLCBmdW5jdGlvbigpIHsgb25fc3RhcnQoKTsgfSwgZmFsc2UpOwoKZnVuY3Rpb24g b25fc3RhcnQgKCkgewogIHZhciBmb28gPSBkb2N1bWVudC5nZXRFbGVtZW50QnlJZCgiZm9vIik7 CgogIHZhciBzZXJpYWxpemVyID0gbmV3IFhNTFNlcmlhbGl6ZXIoKTsKICB2YXIgdGV4dCA9IHNl cmlhbGl6ZXIuc2VyaWFsaXplVG9TdHJpbmcoZm9vKTsKCiAgdmFyIG1hcmt1cCA9IGRvY3VtZW50 LmdldEVsZW1lbnRCeUlkKCJtYXJrdXAiKTsKICBtYXJrdXAuYXBwZW5kQ2hpbGQoZG9jdW1lbnQu Y3JlYXRlVGV4dE5vZGUodGV4dCkpOwoKfQo8L3NjcmlwdD4KPHN0eWxlIHR5cGU9InRleHQvY3Nz Ij4KI21hcmt1cCB7CiAgZm9udC1mYW1pbHk6IG1vbm9zcGFjZTsKICBtYXJnaW4tdG9wOiAyZW07 CiAgd2lkdGg6IDgwJTsKICBwYWRkaW5nOiAxMHB4OwogIGJvcmRlcjogc29saWQgMXB4ICM4ODg7 CiAgYmFja2dyb3VuZC1jb2xvcjogI0RERDsKfQo8L3N0eWxlPgo8L2hlYWQ+Cjxib2R5Pgo8aDE+ VGVzdCBvZiBYTUxTZXJpYWxpemVyPC9oMT4KCjxkaXYgaWQ9ImZvbyI+ClRoaXMgaXMgc29tZSB0 ZXN0IGNvbnRlbnQ8YnIgPgp3aXRoIGEgbGluZSBicmVhay4KPC9kaXY+Cgo8cD5IZXJlIGlzIHRo ZSB0ZXh0IGdlbmVyYXRlZCBieSBYTUxTZXJpYWxpemVyIHNob3dpbmcgaG93CkJSIGlzIHNlcmlh bGl6ZWQgYXMgbWFsZm9ybWVkIFhNTCBhcyAmbHQ7YnImZ3Q7IGluc3RlYWQgb2YKJmx0O2JyIC8m Z3Q7IGFzIGhhcHBlbnMgd2hlbiB5b3UgdmlldyB0aGlzIHBhZ2UgaW4gRmlyZWZveAphbmQgT3Bl cmEuPC9wPgoKPHByZSBpZD0ibWFya3VwIj48L3ByZT4KPC9ib2R5Pgo8L2h0bWw+Cg== 70980 2010-10-17 11:49:46 -0700 2010-10-17 11:49:46 -0700 XHTML test case serialize-br.xhtml application/xhtml+xml 169 ap PGh0bWwgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkveGh0bWwiPgo8aGVhZD48dGl0bGUv PjwvaGVhZD4KPGJvZHk+Cjxici8+CjxzY3JpcHQ+CmFsZXJ0KChuZXcgWE1MU2VyaWFsaXplciku c2VyaWFsaXplVG9TdHJpbmcoZG9jdW1lbnQpKTsKPC9zY3JpcHQ+CjwvYm9keT48L2h0bWw+Cg==