The kinds of events that Chrome makes available to the outside world are different from the events that Firefox makes available.
If you need to wait 3 seconds or more, then most likely as LanX already said, some Javscript only runs after the page is considered complete (by the browser) and then loads additional information. LanX's approach of waiting for a page element is the approach I think is most fruitful. Unfortunately, WWW::Mechanize::Chrome doesn't have the ->wait_until_* methods of WWW::Mechanize::Firefox yet, but maybe you can submit a patch for that?
In reply to Re: Waiting for page to load with WWW::Mechanize::Chrome
by Corion
in thread Waiting for page to load with WWW::Mechanize::Chrome
by nysus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |