WWW-Mechanize-Chrome

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

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

To install WWW::Mechanize::Chrome, copy and paste the appropriate command in to your terminal.

cpanm WWW::Mechanize::Chrome

perl -MCPAN -e shell
install WWW::Mechanize::Chrome

For more information on module installation, please visit the detailed CPAN module installation guide.

	Global
`s`	Focus search bar
`?`	Bring up this help dialog

	GitHub
`g` `p`	Go to pull requests
`g` `i`	go to github issues (only if github is preferred repository)

	Search terms
module: (e.g. module:Plugin)
distribution: (e.g. distribution:Dancer auth)
author: (e.g. author:SONGMU Redis)
version: (e.g. version:1.00)