doesn't parse correctly if whitespaces exist about ltx HOT 4 CLOSED

Not sure I understand. The 2nd example has 3 children: a text node, the <y/> child, and another text node. Why should this be 1?

Squashing whitespace around elements may not be appropriate for all use cases. In XHTML, <b>Hello</b><i>World</i> would be rendered differently from <b>Hello</b> <i>World</i>.

from ltx.

Ok, You're right!
I thought that whitespace/text between two tags (e.g. <a>foo<b/> </a>) is not valid.
So in case my client accidentally added whitespaces (<value> <int>4</int></value>) I'll have problems if I try to access the child by just using it's order

valueElement.children[0] // returns ' ' instead of 4

As long as I know the tag name I can use getChildText("int") otherwise it might be great if there were a method like el.trim() that removes all whitespaces that are not within a tag?

from ltx.

Generally I'd suggest using valueElement.getChild('int'). That way you would assert that the first child is <int/> indeed, not anything else.

A patch for a handy trim() will be accepted!

from ltx.

BTW. As an european open source hacker, do you have any plans regarding FOSDEM 2012? I won't be there, but @dodo is planning to go!

from ltx.