Changelog • chromote

chromote (development version)

Breaking change: Chromote$is_active() method now reports if there is an active connection to the underlying chrome instance, rather than whether or not that instance is alive (#94).

Chromote and ChromoteSession gain print methods to give you a snapshot of the most important values (#140).
Chromote gains a new is_alive() method equivalent to the old is_active() method; i.e. it reports on if there is an active chrome process running in the background (#136).
ChromoteSession now records the targetId. This eliminates one round-trip to the browser when viewing or closing a session. You can now call the $respawn() method if a session terminates and you want to reconnect to the same target (#94).
ChromoteSession$screenshot() gains an options argument that accepts a list of additional options to be passed to the Chrome Devtools Protocol’s Page.captureScreenshot method (#129).
ChromoteSession$screenshot() will now infer the image format from the filename extension. Alternatively, you can specify the format in the list passed to options (#130).
--disable-gpu is no longer included in the default Chrome arguments, except on windows where empirically it appears to be necessary (otherwise GHA check runs never terminate) (#142).

CRAN release: 2023-08-11

Fixed #109: An error would occur when a Chromote object’s $close() method was called. (#110)
Fixed #99: When the $view() method was called, recent versions of Chrome would display "Debugging connection was closed. Reason: WebSocket disconnected". (#101)
Fixed #89, #91: find_chrome() now checks more possible binary names for Chrome or Chromium on Linux and Mac. (thanks @brianmsm and @rossellhayes, #117)
Fixed #22: Added a new chromote.timeout global option that can be used to set the timeout (in seconds) for establishing connections with the Chrome session. (#120)

CRAN release: 2022-09-07

CRAN release: 2022-04-19