Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot
 
PerlMonks  

Re^4: Some issues with WWW::Mechanize::Firefox->xpath() method

by dfaure (Chaplain)
on Apr 02, 2013 at 13:10 UTC ( [id://1026679] : note . print w/replies, xml ) Need Help??


in reply to Re^3: Some issues with WWW::Mechanize::Firefox->xpath() method
in thread Some issues with WWW::Mechanize::Firefox->xpath() method

I'm no expert on XPath and its semantics, but if somebody submits a bug report and preferrably a self-contained example, I can investigate things closer.

You may safely use the code I provided in the OP as example. I'm simply using Firebug+FirePath addons on the target Firefox, to get results from javascript only.

According to https://developer.mozilla.org/en-US/docs/XPCOM_Interface_Reference/nsIDOMXPathResult#Type_constants, I think the problem comes from the parameters given to the XPath evaluator, which limits the retrieved elements to nodesets. IMHO, the solution would be to use XPathResult.ANY_TYPE and perhaps a more elaborated function than identity to build the result set.

Should I open a bug on RT for this?

____
HTH, Dominique
My two favorites:
If the only tool you have is a hammer, you will see every problem as a nail. --Abraham Maslow
Bien faire, et le faire savoir...

  • Comment on Re^4: Some issues with WWW::Mechanize::Firefox->xpath() method