You must be doing something wrong then, because I use it to automate Javascript-heavy websites. Maybe if you showed the code you've been using to "test" this, I could show you your error. Most likely, you've been using repeated calls to ->get, which are akin to pasting an URL into the browser, instead of using ->click() on the appropriate DOM models. But then again, comparing what gets sent over the wire using one method or the other would even allow you to replicate the whole scenario using WWW::Mechanize, and it seems you haven't looked at what gets actually sent to determine the cause of the difference. Use Wireshark or the Mozilla Live HTTP Headers extension to inspect what gets sent to the server by the browser.

Hmmm, I guess I kind of fibbed, in that my test was typing the url's into the browser, because I knew this was the same as a call to ->get() and I didn't realize there was another way to navigate. That'll teach me to think I know it all.

So I decided to actually take the module for a spin, but now I'm having a really perplexing problem. I seem to have lost to ability to call subroutines from another module. I figure since my current problem is pretty unrelated to this thread I should create a new one, in the seekers of wisdom section.