The reason that enabled popup is in "contrib" is to indicate that it is
unsupported code.
I've never used Watir's modal dialog support for production testing
(except for showModalDialogs, which i've used and which IMHO has
excellent support). The support for the other modal dialogs needs work
simply for IE much less working on how to make this work cross-platform.
Some of this code is not in contrib, although it probably should be.
I've always found it easier to avoid dealing with modal dialogs, so I've
never had personal motivation to work on this code.
I've considered removing the nascent support for modal dialogs from
Watir entirely (perhaps bundling as a separate gem), to help telegraph
that this code is not being maintained or supported. Perhaps this would
help this code find a new owner.
Bret
Lisa Crispin wrote:
> Hi Bret,
> Just to clarify - So for now we have to use require 'watir\ie' in
> order to require 'watir\contrib\enabled_popup', but in the next
> version, we won't have to use require 'watir\ie', correct?
>
> My next question may be ignorant - if we want to be able to run our
> scripts in firewatir as well as watir, does that mean we can't use
> this enabled_popup thing to deal with modal dialogs? In that case, how
> DO we deal with modal dialogs?
> thanks,
> Lisa
>
> On Thu, Nov 13, 2008 at 11:06 AM, Bret Pettichord <
br...@pettichord.com
> <mailto:
br...@pettichord.com>> wrote:
>
>
> i've added the require statement to the enabled popup script
> itself, so
> this workaround will not be required with the next version of watir
>
> jpweston wrote:
> > Thanks for this and your explanation in the "Uninitialzied Constant"
> > post.
> >
> > j.
> >
> > On Nov 12, 9:17 pm, Bret Pettichord <
b...@pettichord.com