Are you using verifyConfirmation/verifyAlert? It is not clear from your posting, and you need to use this to clear the alert or confirmation. If you do not care about the wording of the alert/confirmation, you can always use '*' to match all.
Does the alert happen in an onblur() event of an input field? I seem to recall having trouble with an app that popped up an alert in the onblur event of an input field and returned focus to that field. Selenium used to scroll the command list by "focussing" on the next command, and this would trigger another onblur event, but I think we fixed this problem some time ago by using scrollIntoView().
I think we also have an existing Jira issue to do with the problem that, if your test ends with an unverified alert or confirmation, then the start of the next test will fail. Ideally, Selenium should check that all alerts and confirmations have been verified when it reaches the end of a test.
David Kemp
ThoughtWorks Australia Pty Ltd
http://www.thoughtworks.com
[EMAIL PROTECTED] wrote on 01/10/2005 06:38:44 AM:
> I submitted a JIRA issue yesterday for this bug and wonder if anyone
> else has encountered it and found a work-around.
>
> The first time the form generates a confirmation, selenium handles it
> automatically as advertised. The next one throws the error, "There
> was an unexpected Confirmation!" (This isn't the only situation it's
> happened to me, but a good example.)
>
> It seems that somehow selenium isn't resetting the handling of the
> confirmation box somehow.
>
> Thanks,
>
> Jamie
>
> Mac OS X 100.4.2, Firefox
> _______________________________________________
> Selenium-users mailing list
> Selenium-users@lists.public.thoughtworks.org
> http://lists.public.thoughtworks.org/mailman/listinfo/selenium-users
_______________________________________________ Selenium-users mailing list Selenium-users@lists.public.thoughtworks.org http://lists.public.thoughtworks.org/mailman/listinfo/selenium-users
