Closed iambodi closed 2 years ago
the second //*[contains(@id,"food")]
including current self node
when searching matches node, the correct should only process child of matched node by the first //*[contains(@id,"food")]
, not self
. That is why your xpath can return a matched node.
Thank you for your quick response ! Ok, so just to be sure : this is a bug, right ? If so, do you think it could be fixed in the near future ? I took a look at the code but couldn’t find what’s causing this behavior.
checkout https://github.com/antchfx/xpath/commit/ba368a603dd4fbdce369eb76a2636e41444a929b to fix.
You can re-open it if not fix.
Hi,
I have an issue with the
Find
method. When passed an invalid xpath (confirmed by the HTML inspector of Chrome and Firefox), it returns a node.On playground: https://go.dev/play/p/3Z6jtSNsYfx
Thank you !