You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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 !
The text was updated successfully, but these errors were encountered: