problem

Assume a segment like that:

Test text <1><2><3/></2></1> or <4><5><6/></5></4>. 

When finding a fuzzy match in the TM (same tags, slightly different text) and taking over that segment in the UI from the match resource panel, we get in the segment editor then:

Different text <1><2><3/></2></1> or <4><5><3/></5></4>.  

Please note, that the <6/> tag is gone and replaced by <3/> - which is then twice in the segment. According to the segment history the user did fix that in the same editing process, so the user repaired the tags, removed the second <3/> tag and replaced it with <6/> tag. Still the way how he did that (ctrl-c,ctrl-v or ctrl-, 6) is unclear.

However, after saving the tag should look correct, but the div span CSS container of the second tag is containing the css content of the previous <3/> tag which is wrong.