Re^3: WWW::Mechanize::Chrome VERY slow on xpath obtaining TDs of a TR

I will try this, thank you!

I noticed that fetching the TRs of the table seems pretty fast with WWW::Mechanize::Chrome and xpath. What's seems absurd is that fetching the TDs relative to a single TR takes so long, and the time is proportional to the number of total TRs. That doesn't make any sense unless there's a bug somewhere in WWW::Mechanize::Chrome xpath implementation.

Comment on Re^3: WWW::Mechanize::Chrome VERY slow on xpath obtaining TDs of a TR

Replies are listed 'Best First'.
Re^4: WWW::Mechanize::Chrome VERY slow on xpath obtaining TDs of a TR by LanX (Saint) on Nov 25, 2022 at 14:53 UTC
I can't look into it now, so some general advice Try the Xpath inside the browser's dev console Try logging what mechanize does under the hood. Back in the time when I used W:M:FF I was able (and sometimes needed) to send and eval JS and fetch the result as JSON. All this will help you specifying a feature request (if needed) for W:M:C HTH :) Cheers Rolf _{(addicted to the 𐍀𐌴𐍂𐌻 Programming Language :) Wikisyntax for the Monastery}	[reply]
Re^5: WWW::Mechanize::Chrome VERY slow on xpath obtaining TDs of a TR by ait (Hermit) on Nov 25, 2022 at 15:35 UTC
Thank you! I'm on a tight schedule to deliver so I think I'm going with extracting the HTML of the table with W::M::Chrome and parsing it with HTML-Tree I'll post my solution in the OP so that can help others in the future.	[reply]
Re^5: WWW::Mechanize::Chrome VERY slow on xpath obtaining TDs of a TR by ait (Hermit) on Nov 25, 2022 at 15:37 UTC
If I get a good payday from this small gig, I'll look into the W::M::Chrome code myself and see if I can at least contribute in some way...	[reply]