Parser error reported for computed element constructors in XPath steps

[willsthompson]

Direct element constructors are handled correctly in XPath expressions:

<a><x>test</x></a>/x/node()/<a>{ . }</a>

But an error is generated for equivalent expressions using computed element constructors, except for those at the beginning of an expression. Here, the first pair of nested element constructors are handled, but the one in the last step generates a parser error:

element a { element x { 'test' }}/x/node()/element a { . }