[
Lists Home |
Date Index |
Thread Index
]
> > Technically, I think we're compliant, but it sure can annoy the
> > user. ;)
>
> It would certainly be annoying if, for example, (//foo)[4] didn't
> return the 4th foo element in the document, because it wouldn't be
> compliant.
>
> In the XPath 1.0 spec it states that a Predicate on an expression (as
> here) filters the node-set with respect to the child axis [1]. The
> child axis is a forward axis, so the nodes must be arranged in
> document order when assessing their position [2].
Howsabout given:
(//foo | //bar)[4]
Would that be the 4th occurrence of either foo or bar, in document
order? That's just an implementational nightmare.
-bob
|
