Comment 3 for bug 1684273

I agree that this is unexpected. It can be fixed by internally passing more data into the parser before generating the "end" parse event, i.e. by waiting for the tail text to end before yielding the element that owns it.