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

Changes for version 0.48 - 2020-04-19

  • API CHANGES:
  • ->field() now takes the form field index as third parameter, like WWW::Mechanize does. It warns about the old usage and corrects it for the time being. Change ->field( name => 'John Bull', [], [] ) to ->field( name => 'John Bull', undef, [], [] ) for operating as it did before and silencing the warning.
  • ->field() now checks its parameter count and wants a field name and a value to set the field to. Use ->value() to query the value of a field without setting it. This change to your scripts is mandatory because ->field() now uses a parameter declaration.
  • ->value() now takes the index as its second parameter, instead of taking a new value as its second parameter. The old form was deprecated a long time ago.
  • ->set_fields() now can set the value of fields with the same name ->set_fields( foo => ['new_value', 2] ) now works.
  • Stability fixes/warning elimination in ->handle_dialog() and ->_handle_screencast_frame() The methods used their hand-rolled handling of "fire-and-forget" Futures instead of using Future->retain()
  • Temporarily add Data::Dump as test prerequisite. This seems to be an action that will prevent test failures on Travis: https://rt.cpan.org/Public/Bug/Display.html?id=132378

Documentation

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

Modules

Chrome::DevToolsProtocol
asynchronous dispatcher for the DevTools protocol
Chrome::DevToolsProtocol::Target
wrapper for talking to a page in a Target
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
choose the best pipe transport backend
Chrome::DevToolsProtocol::Transport::Pipe::AnyEvent
Chrome::DevToolsProtocol::Transport::Pipe::Mojo
EXPERIMENTAL Local pipe backend for Chrome communication
Chrome::DevToolsProtocol::Transport::Pipe::NetAsync
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
WWW::Mechanize::Chrome::URLBlacklist
blacklist URLs from fetching

Provides

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

Examples

Other files