|
40f58521
|
2017-05-26T20:16:35
|
|
Fix axis traversal from attribute and namespace nodes
When traversing the "preceding" axis from an attribute node, we must
first go up to the attribute's containing element. Otherwise, text
children of other attributes could be returned. This made it possible
to hit a code path in xmlXPathNextAncestor which contained another bug:
The attribute node was initialized with the context node instead of the
current node. Normally, this code path is only hit via
xmlXPathNextAncestorOrSelf in which case the current and context node
are the same.
The combination of the two bugs could result in an infinite loop, found
with libFuzzer.
Traversing the "following" and the "preceding" axis from namespace nodes
should be handled similarly. This wasn't supported at all previously.
|
|
|
342658a1
|
2015-03-08T16:46:04
|
|
Add a couple of XPath tests
|
|
|
f6aaabce
|
2015-03-08T16:05:26
|
|
Allow attributes on descendant-or-self axis
If the context node is an attribute, the attribute itself is on the
descendant-or-self axis. The principal node type of this axis is element,
so the only node test that can return the attribute is "node()". In other
words, "@attr/descendant-or-self::node()" is equivalent to "@attr".
This matches the behavior of Saxon-CE.
|
|
b96e6438
|
1999-08-29T21:02:19
|
|
Release 1.6, lot of fixes, more validation, code cleanup, added namespace
on attributes, Daniel.
|
|
|
b05deb7f
|
1999-08-10T19:04:08
|
|
Huge commit: 1.5.0, XML validation, Xpath, bugfixes, examples .... Daniel
|
|
|
1566d3a9
|
1999-07-15T14:24:29
|
|
Added XPath code (http://www.w3.org/TR/xpath), updated HTML support and docs, Daniel
|