I agree with the sentiment. One of the troubles is that there are lots of conflicting monkey patches out there for the wait method. So it really should be refactored into a composed method to make it easier to combine modifications.
Bret On Wed, Feb 17, 2010 at 2:20 AM, Jarmo <[email protected]> wrote: > Is it really needed to have it possible to configure (e.g. writing new > code which is not needed in the future)? Just create one monkey-patch > what would be possible to require in if wanted and that's it. Or might > there be any problems with that temporary solution? > > Jarmo > > > I think this is the correct documentation. > > > http://msdn.microsoft.com/en-us/library/system.windows.forms.webbrowserreadystate.aspx > > > It does imply that ReadyState == 3 might be fine. > > > I suggest we make this user-configurable in Watir, so that we get more > > people to give it a shot, before we change the default behavior. > > > Bret > _______________________________________________ > Wtr-development mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/wtr-development > -- Bret Pettichord Lead Developer, Watir, www.watir.com Blog, www.io.com/~wazmo/blog Twitter, www.twitter.com/bpettichord
_______________________________________________ Wtr-development mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-development
