1) MacOS
2) I have a copy of Chromium installed exclusively for use by W::M::C.
I haven't written it with the public in mind and it has some custom code specific to me. But if you download it, you can get it to work with minimal hacking. Specifically, the internal _quit function uses some custom code for use by me to run a wrapper script for the osascript function. You will definitely want to change this to something normal like:
system ('osascript -e \'quit app "Chromium"\''); # this is untested
There isn't a lot to this module and can be easily adapted to other OSes and browser configurations.
I wrote a little utility for myself to prepare Chromium for use by W::M::C:
https://github.com/sdondley/WWW-Mechanize-Chrome-PrepareChromium
Might be useful to others with same set up as me:
1) MacOS 2) I have a copy of Chromium installed exclusively for use by W::M::C.
I haven't written it with the public in mind and it has some custom code specific to me. But if you download it, you can get it to work with minimal hacking. Specifically, the internal
_quit
function uses some custom code for use by me to run a wrapper script for theosascript
function. You will definitely want to change this to something normal like:system ('osascript -e \'quit app "Chromium"\'');
# this is untestedThere isn't a lot to this module and can be easily adapted to other OSes and browser configurations.