[XSLT] Need to say what happens when a capturing accumulator rule matches a non-element node

[michaelhkay]

[XSLT] Need to say what happens when a capturing accumulator rule matches a non-element node

[ndw]

Why is that better than just making the node available?

[michaelhkay]

The node is available anyway; capture="yes" in this case is logically a no-op. The only question is, its presence suggests some kind of misunderstanding on the users' part, so should we flag it?

[ndw]

It's an interesting question. I can imagine enabling capture even when I'm using a rule that matches, say, a text node. Possibly because there are other rules that match trees and I'm being careless. But flagging things that suggest a misunderstanding of what an expression is going to do certainly has benefits. "Whaddya mean that's...oooohhh!"

[Arithmeticus]

Someone who writes <xsl:accumulator-rule match="node()[string-length(.) lt 5]" phase="end" capture="yes"> would not appreciate an error for matches on a text node, no?