innerHTML doesn't work correctly w/ xhtml namespaces See attached test case.
Created attachment 4050 [details] test case
Created attachment 5483 [details] Fix This changes parseXMLDocumentFragment back into using xmlParseBalancedChunkMemory, because using the regular parser does not work for things such as "<foo/><foo/>" which are legal fragments. This does break the XSLTProcessor test, but that's because of a bug in XLSTProcessor which I'm investigating
Comment on attachment 5483 [details] Fix Bad to regress the XSLTProcessor tests. Let's fix those issues first.
If the patch in 6180 is committed, the XSLT test won't fail anymore. (The reason was that the garbage produced does not parse as a fragment, but as a document)
Comment on attachment 5483 [details] Fix Now that #6180 has been fixed, this does not cause a regression anymore
Comment on attachment 5483 [details] Fix Please post an updated patch w/o these (now invalid) test changes.
Created attachment 5491 [details] Remove invalid test result
Comment on attachment 5491 [details] Remove invalid test result IMO, any balanced handlers which can be the same as the normal handlers should be. I think most of these can share code there.
Comment on attachment 5491 [details] Remove invalid test result Otherwise the patch looks great!
Comment on attachment 5491 [details] Remove invalid test result It isn't possible to share them, because the normal handlers have a context pointer as user data arguments to make it possible for the regular libxml SAX handlers to be called. It isn't possible to create such a context pointer when parsing a balanced chunk.
Comment on attachment 5491 [details] Remove invalid test result Ah yes! I remember that exact issue w/ the userdata vs. context pointer. Looks good. r=me.
Mass moving XML DOM bugs to the "DOM" Component.