I'm sure this issue can be addressed pretty easily (and it's probably just a test failure, not a module failure). That said, I once tried to use WWW::Mechanize::Chrome and ended up switching to Selenium::Chrome. It worked far better (though I don't remember the details). (See Selenium::Remote::Driver for documentation on the methods provided by Selenium::Chrome.)