XmlStream unexpected round-trip output when configuring empty element with [INLINE, EXCLUDE]

[Former user]

Original issue 290 created by @fliden on 2012-11-12T23:36:04.000Z:

One engineer noticed that when configuring an empty element such as <x/> with [INLINE, EXCLUDE] it disappears from the round-trip output.

Changing it to <x></x> seems to work to maintain it. But logically they are the same so perhaps both cases should work.

One solution is to change the configuration to just [INLINE]. But if you're looking for actual[INLINE, EXCLUDE] behavior and you happen to have cases of empty tags <x/> (some tools might condense empty elements) then they get lost.

Not sure yet if it's a problem with the filter or if it's the rtf/xliff writer (inner outer codes). Just making a note of it for now. It's not that common i think so not urgent.

[Former user]

Comment 1. originally posted by @ysavourel on 2012-11-13T00:28:59.000Z:

Likely this is an AbstractMarkup issue - but I thought we had a test case for this already in M19

[Former user]

Comment 2. originally posted by @ysavourel on 2012-11-13T19:44:48.000Z:

fixed by ending code in the start tag handler if the tag is standalone

[Former user]

Comment 3. originally posted by @ysavourel on 2012-11-13T19:45:55.000Z:

This issue was closed by revision 281bbc4cf82a.