comment on

I recently tried Win32::IE::Mechanize but it didn't work for me. In the docs it says:

The InternetExplorer automation object does not provide an interface to "popup windows" generated by security settings or JScript contained in the page.

The InternetExplorer automation object does not provide an interface to the content of frames from the toplevel document. This means that you need to load the frame explicitly (using the follow_link() method).

The basic authentication support is quite wonky and will only work with the get() method

Win32::IEAutomation has popup functions, accepts pretty much all js, works perfectly with frames, authentication is solid and is a lot simpler to use, IMO.

It might not offer as many possibilities as Win32::IE::Mechanize, but it fits my needs perfectly. Recommended to anyone (working on windows) who wants to grab pages containing js.

teabag
Blessed is the end user who expects nothing, for he/she will not be disappointed.

In reply to Re: Win32::IEAutomation vs Win32::IE::Mechanize by teabag
in thread Win32::IEAutomation vs Win32::IE::Mechanize by szabgab

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Just another Perl shrine
	PerlMonks