in reply to [solved] WWW::Mechanize::Firefox->new() tcp/ip port?

My personal advice is to avoid mixing fork and WWW::Mechanize::Firefox, unless you fork way before creating the connection to Firefox.

The WWW::Mechanize::Firefox documentation specifies the repl parameter, which allows you to pass in:

repl - a premade MozRepl::RemoteObject instance or a connection string suitable for initializing one

I wonder how that could be formulated to be more clear so that you yould have found it directly.

Replies are listed 'Best First'.
Re^2: WWW::Mechanize::Firefox->new() tcp/ip port?
by ground0 (Novice) on Mar 25, 2013 at 21:29 UTC

    I tried with repl => "localhost:port" and I get same mixup. Somehow when $html = $mech->content happen in each fork it get confused and mix up all the $html.

    This make it so my temporary sanitized html files have wrong document element mixed in.

    Since this happen *in* the fork I guess I misunderstand when you say do way before the fork! :)

    PS) I forgot to mention this inside a *nested* fork, if that matter.
[reply]
[d/l]
[select]

      Then maybe that mixup is not connected with how you construct your WWW::Mechanize::Firefox object?

[reply]
[reply]

In Section Seekers of Perl Wisdom