/ 
WWW-Mechanize-Chrome-0.36
River stage one • 4 direct dependents • 4 total dependents
⭐ Starred 30 GitHub stars

Changes for version 0.36 - 2019-09-27

  • Added cleanup_signal option to select the signal which is used for cleaning up Chrome instances. This is SIGKILL on Windows and SIGTERM everywhere else by default. Proposed and prototyped by Chris Novakovic.
  • First parts of talking to Chromium via IPC pipes instead of sockets The real change will come in the next versions, but you can enable using a pipe for communication already by using the pipe => 1 option.
  • More lenient timeouts
  • Fix retrieving the Chrome version There was a spurious call to ->log() when we didn't have a logger. This resulted in empty Chrome versions.

Documentation

WWW::Mechanize::Chrome::Contributing
WWW::Mechanize::Chrome::Install

Modules

Chrome::DevToolsProtocol
asynchronous dispatcher for the DevTools protocol
Chrome::DevToolsProtocol::Transport
choose the best transport backend
Chrome::DevToolsProtocol::Transport::AnyEvent
AnyEvent backend for Chrome communication
Chrome::DevToolsProtocol::Transport::Mojo
Mojolicious backend for Chrome communication
Chrome::DevToolsProtocol::Transport::NetAsync
IO::Async backend for Chrome communication
Chrome::DevToolsProtocol::Transport::Pipe
EXPERIMENTAL Local pipe backend for Chrome communication
HTTP::Cookies::ChromeDevTools
retrieve cookies from a live Chrome instance
WWW::Mechanize::Chrome
automate the Chrome browser
WWW::Mechanize::Chrome::Cookbook
Getting things done with WWW::Mechanize::Chrome
WWW::Mechanize::Chrome::DSL
Domain Specific Language for short scripts
WWW::Mechanize::Chrome::Examples
WWW::Mechanize::Chrome example programs.
WWW::Mechanize::Chrome::Node
represent a Chrome HTML node in Perl
WWW::Mechanize::Chrome::Troubleshooting
Things to watch out for

Provides

Win32::InheritHandles
in lib/Chrome/DevToolsProtocol/Transport/Win32PipeOpener.pm

Examples

Other files