in reply to editing an article that also uses javascript with mechanize

I'm sure I must have said this before, maybe to your alter ego, but if you use Win32::IE::Mechanize instead of WWW::Mechanize, the former is based on the MSIE core and it will process Javascript before handling the result to you. The disadvantage is that it'll only work on Windows. It's not an exact plugin replacement, either, due to the differences in their cores. So it'll require some manual tweaks to make it work.
  • Comment on Re: editing an article that also uses javascript with mechanize

Replies are listed 'Best First'.
Re^2: editing an article that also uses javascript with mechanize
by adrianh (Chancellor) on Aug 09, 2006 at 08:20 UTC
    I'm sure I must have said this before, maybe to your alter ego, but if you use Win32::IE::Mechanize instead of WWW::Mechanize, the former is based on the MSIE core and it will process Javascript before handling the result to you. The disadvantage is that it'll only work on Windows.

    There's also Selenium (in combination with WWW::Selenium, WWW::Selenium::Utils, Test::WWW::Selenium, etc.). Drives the browser using JavaScript, so works on several different platforms.

    There's also wtr which is written in Ruby and, like Win32::IE::Mechanize drives MSIE directly. IMO it has a nicer API - but opinions may vary ;-)