Changes for version 0.31 - 2019-05-25
- Silence HTTP::Cookies::Chrome debug output left over
- ->eval() now takes options on whether object references or JSON-serialized data should be returned. This allows you to reference the "window" object, for example. Currently, these object references are kept as hashrefs instead of objects, and the handling needs to become more transparent with respect to the Chrome API, but that is planned for later versions.
asynchronous dispatcher for the DevTools protocol
choose the best transport backend
AnyEvent backend for Chrome communication
Mojolicious backend for Chrome communication
IO::Async backend for Chrome communication
retrieve cookies from a live Chrome instance UNAUTHORIZED
automate the Chrome browser
Getting things done with WWW::Mechanize::Chrome
Domain Specific Language for short scripts
WWW::Mechanize::Chrome example programs.
represent a Chrome HTML node in Perl
Things to watch out for