Not sure whether this was an intention. but strictly speaking, new behavior is correct. See Extensible Markup Language (XML) 1.0 (Fifth Edition), Section 2.10 White Space Handling: "An XML processor must always pass all characters in a document that are not markup through to the application. A validating XML processor must also inform the application which of these characters constitute white space appearing in element content." Jan On Mon, 2016-04-25 at 12:14 +0200, Cyril Ferlicot Delbecque wrote:
Hi,
last week there was a new stable version of XMLParser and some tests broke in some tools. I think that there was a regression in this version.
Snippet:
(XMLDOMParser parse: '<?xml version="1.0" encoding="UTF-8"?> <!--clones description file--> <Clones> Â Â Â Â <ClonedFragment cloneName="test"> Â Â Â Â Â Â Â Â <Member fileName="ProgramA"/> Â Â Â Â Â Â Â Â <Member fileName="ProgramB"/> Â Â Â Â </ClonedFragment> Â Â Â Â <ClonedFragment cloneName="test2"> Â Â Â Â Â Â Â Â <Member fileName="ProgramA"/> Â Â Â Â Â Â Â Â <Member fileName="ProgramB"/> Â Â Â Â </ClonedFragment> </Clones>') elements first nodes
With the release 2.7.4 we get 2 nodes but in release 2.7.6 we get 5 nodes. The 2 previous ones and 3 empty String nodes.
I think this is not what we expect. Correct me if I am wrong :)