Re: Issue 3392 in selenium: Allow capability to specify auto-dismiss behaviour on UnhandledAlertException

[sele...@googlecode.com]

Updates:
Summary: Allow capability to specify auto-dismiss behaviour on
UnhandledAlertException
Status: New
Labels: -Type-Defect -Browser-Atoms Type-Enhancement

Comment #10 on issue 3392 by dawa...@gmail.com: Allow capability to
specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

(No comment was entered for this change.)

[sele...@googlecode.com]

Comment #12 on issue 3392 by dawa...@gmail.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Issue 3600 has been merged into this issue.

[sele...@googlecode.com]

Comment #13 on issue 3392 by tom.art...@gmail.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Thank you!

[sele...@googlecode.com]

Comment #14 on issue 3392 by mgoodno...@gmail.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Also waiting patiently for change. My usage is to handle the browser
authentication dialog which pops up. It's a very nice feature to
auto-dismiss unexpected dialogs, but yes we do need option to handle those
which are expected.

If I could make driver wait at least 30 seconds before dismissing that
would solve my problem. -dawagner- your comment on Feb 28 was to set the
WebDriverWait but I tried all the wait options I could find but no luck,
WebDriver is still dismissing authentication dialog as soon as it opens
(need it to wait at least 30 sec). Is a wait option available?

Many thanks for all the work!

[sele...@googlecode.com]

Comment #15 on issue 3392 by shine...@hotmail.it: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Hi i'm having the same issues. I have a form to compile and then i have to
press a save button that run a javascript code to save the informations.
I have a test to test all the alert that can occur by validating the save
process and the informations provided.
I'm using a Javascript Executor to run javascript code without pressing the
button and the problem i have is kinda wierd.
If i use JsExecutor, the first time it gives me an exeption(that means that
he has not found the javascipt code i m calling). If i press the button
calling the same function there is no problem about javascript code even if
the next alert are generated by JsExecutor.Further more i have the same
problem discussed in this page since chrome auto-rejects the first alert. I
decided then to catch that exception(UnhandeledAlertExc.) but there is
still the problem only for the first alert but not for the others. I've
tried also to swap the order of alerts activation but i have the same
results(the first alert not handled).
It's also kinda wierd that you shuold work with alert throught the
exception that they can raise =)
I hope you gonna fix it cause chrome webdriver is really faster than
firefox's.
Thanks for the great job u made until now, best regards.

[sele...@googlecode.com]

Comment #16 on issue 3392 by jragha...@gmail.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

It will be nice if we find a fix for this issue soon.
Cuz people in forums are finding issue as a show stopper.

https://groups.google.com/forum/?fromgroups#!topic/selenium-users/u3ayBQrYvOg

https://groups.google.com/forum/?fromgroups#!topic/webdriver/dxImsuPHni8

[sele...@googlecode.com]

Comment #17 on issue 3392 by PhanDinh...@gmail.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

I got the same issue when the alert just occurs under some circumstances.
The only solution is waiting in a blind period! So it would be great if you
fix this issue soon.
Thanks!

[sele...@googlecode.com]

Comment #18 on issue 3392 by jragha...@gmail.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

I request this issue to have priority set as High.

Just tested will the latest versions from Selenium 2.18 to 2.22 all
automatically closing pop up window boxes. This causes big problem in our
cause when it comes to a certificate pop up window. We are using AutoIT
script for selecting Certificates we need. Now, since after upgrading to
latest jar selenium closes the certificate window automatically we left
with no work around for this.

[sele...@googlecode.com]

Comment #19 on issue 3392 by dawa...@gmail.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Issue 4098 has been merged into this issue.

[sele...@googlecode.com]

Comment #20 on issue 3392 by gone...@gmail.com: Allow capability to specify

auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Tested with 2.24.1 - The problem still there.

[sele...@googlecode.com]

Comment #21 on issue 3392 by zawai...@gmail.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

This should be a considered a regression, not just an enhancement. When
doing acceptance testing, many-times we test both the accept and dismiss
behavior. This is simply not possible since 2.18.0.

[sele...@googlecode.com]

Comment #22 on issue 3392 by barancev: Allow capability to specify

auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

"Regression" is something that had been working in past but was broken.
This fieature never existed before, it's a new beast.

And it's implemented in 2.25 for FF browser.
Other browsers are coming later.

[sele...@googlecode.com]

Comment #23 on issue 3392 by pemberto...@gmail.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

That's awesome news, is there any ETA on it being implemented on the IE
browser?

[sele...@googlecode.com]

Updates:
Labels: Browser-IE Browser-Chrome

Comment #24 on issue 3392 by barancev: Allow capability to specify

auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

[sele...@googlecode.com]

Comment #25 on issue 3392 by richard....@ca.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

The auto-dismissal of the IE Windows Security dialog is also killing my
test scripts. This is a regression of previous vital functionality (albeit
caused by intro of a new feature). Can't believe it's gone unfixed for so
long, if I was evaluating selenium for test automation right now I'd throw
it out on the basis of this bug.

Any ETA for the IE driver fix please?

[sele...@googlecode.com]

Comment #26 on issue 3392 by james.h....@gmail.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

The IEDriverServer.exe has had the ability to set this behavior since
2.25.3. You can set it via the "unexpectedAlertBehaviour" capability. Valid
values are "ignore", "accept", or "dismiss".

[sele...@googlecode.com]

Comment #27 on issue 3392 by alladi....@gmail.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Still i am facing the same issue after set the capability to the "ignore".
It's still dismissing the alert box.

below is the code which i am using for the ignore the alert box click
action test

InternetExplorerOptions theOptions = new InternetExplorerOptions();
DesiredCapabilities ieCapabilities =
theOptions.ToCapabilities() as DesiredCapabilities;

ieCapabilities.SetCapability("unexpectedAlertBehaviour", "accept");
InternetExplorerDriver theDriver = new
InternetExplorerDriver(theOptions);
theDriver.Navigate().GoToUrl("xyz")


Note :-
I am using the Selenium-dontnet-2.25.1
with IeDriver as : IEDriverServer_Win32_2.25.3

[sele...@googlecode.com]

Comment #28 on issue 3392 by richard....@ca.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Is that a typo above?
You say you want to ignore the alerts but your example code sets:

ieCapabilities.SetCapability("unexpectedAlertBehaviour", "accept");

That should be "ignore".

[sele...@googlecode.com]

Comment #29 on issue 3392 by alladi....@gmail.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Hi Richard,

By mistake i have written "accept" instead off "ignore". In reality in my
code it is "ignore" only.

Regard's
Sai baba

[sele...@googlecode.com]

Comment #30 on issue 3392 by richard....@ca.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Sai baba, the code below seems to work for me; in that at least I now see
the login dialog appear and not get dismissed unless I explicitly close it.
There does still seem to be a behavioural oddity though and the script
doesn't run reliably without that Thread.sleep() after the get(url) call.
That really shouldn't be necessary but Selenium doesn't seem to wait for
the dialog to be dismissed and the page to load without it.

DesiredCapabilities ieCapabilities = DesiredCapabilities.internetExplorer();
ieCapabilities.setCapability(CapabilityType.UNEXPECTED_ALERT_BEHAVIOUR, "ignore");
driver = new InternetExplorerDriver(ieCapabilities);

mDriver.get(mURL);
Thread.sleep(10000);

[sele...@googlecode.com]

Comment #31 on issue 3392 by alladi....@gmail.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Hi Richard,

Can you please tell me which version of the Selenium-dontnet are you using?
Because ,when i check with Selenium-dotnet-2.25.1 version, i am not able to
get the capability option of "CapabilityType.UNEXPECTED_ALERT_BEHAVIOUR,"
and there is no overloaded constructor which support
the "DesiredCapabilities" as a parameter for InternetExplorerDriver.

[sele...@googlecode.com]

Comment #32 on issue 3392 by pemberto...@gmail.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Hi,

The code I am using that works is:

DesiredCapabilities desiredCapabilities =
DesiredCapabilities.InternetExplorer();
desiredCapabilities.SetCapability("unexpectedAlertBehaviour", "ignore");

[sele...@googlecode.com]

Comment #33 on issue 3392 by richard....@ca.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Sai Baba - I use Java not DotNet but tend to install the
selenium-server-standalone package so I'm using 2.25.0 (IEDriverServer
2.25.3).
With Java the support for passing InternetExplorerDriver(ieCapabilities)
has been around for a long time though. I'm surprised dotnet doesn't allow
the same.

Pemberto - I tried exactly that first out:
DesiredCapabilities.SetCapability("unexpectedAlertBehaviour", "ignore");
But Java doesn't have a method that allows (String, String) to be passed. I
needed (Capability Name, Value) where value could be String, Boolean or
Object.

[sele...@googlecode.com]

Comment #34 on issue 3392 by alladi....@gmail.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Richard :- There is no support with "ieCapabilites" in
Selenium-dotnet-2.25.1 version. It support InternetExplorerOptions class
as a parameter, i have tried with this option, but no luck.

Can some one tell me whether Selenium-dotnet-2.25.1 version
support "unexpectedAlertBehaviour" option or not.

[sele...@googlecode.com]

Comment #35 on issue 3392 by jfa...@gmail.com: Allow capability to specify

auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Is the "ieCapabilities" & "unexpectedAlertBehaviour" built into the Ruby
bindings yet? If so can someone help out with a code snippet of how to do
this in Ruby?

[sele...@googlecode.com]

Comment #36 on issue 3392 by kuruvila...@gmail.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Bindings : java, Version : 2.26.0, OS : XP, Browser : IE8

When i use "unexpectedAlertBehaviour" capability with
values "accept", "dismiss" or "ignore" the alert is accepted, dismissed or
ignored. But all methods after that is causing the Execption

org.openqa.selenium.UnhandledAlertException: Modal dialog present

[sele...@googlecode.com]

Comment #37 on issue 3392 by alladi....@gmail.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Hi kuruvila,

Even i am facing the same issue,with the Dotnet 2.26.0 version.

Regard's

Sai baba

[sele...@googlecode.com]

Updates:
Labels: -Browser-IE

Comment #38 on issue 3392 by barancev: Allow capability to specify

auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

It's working as designed -- "unexpectedAlertBehaviour" capability defines
what should be done *in addition* to throwing UnhandledAlertException
exception.

[sele...@googlecode.com]

Comment #39 on issue 3392 by dine...@gmail.com: Allow capability to specify

auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Is it possible set unexpectedAlertBehaviour to Ruby?

I tried but failed with cucumber/capybara



--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[sele...@googlecode.com]

Comment #40 on issue 3392 by saileshj...@gmail.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

same here,i tried with cucumber/capybara but it failed. Selenium web-driver
2.33

[sele...@googlecode.com]

Comment #41 on issue 3392 by jbeja...@gmail.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

const string iePath =
@"..\..\..\..\packages\WebDriver.IEDriver.32-bit.2.33.0\tools";
var options = new InternetExplorerOptions
{
UnexpectedAlertBehavior =
InternetExplorerUnexpectedAlertBehavior.Accept
};
ScenarioContext.Current["browser"] = new
InternetExplorerDriver(iePath, options);

[sele...@googlecode.com]

Comment #42 on issue 3392 by patr...@3qilabs.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

This is definately a show-stopper.
Even more so if the current behavior propogates to the FF and IE drivers.

I'm not sure this issue is completely understood.

I think we need to be able to decide how to handle an alert/confirmation
each time one comes up in the way appropriate for that specific instance of
an alert.

If 'ignore' throws the the UnhandledAlertException we should be able to
catch it (in whatever language we are using, I'm using Ruby) and decide
what to do right there.

The alert should _not_ just go away. It should be available for something
like 'browser.alert.ok'.

Handling all alerts as unexpected and throwing an exception tends to force
every method doing an action (setting a field, clicking an element, etc.)
to catch the exception. If that is the only way to handle it then at
least provide a setting to allow the exceptions to be caught.

Perhaps a 'manual' option is in order:
Possible behavior:
= 'accept': all alerts are accepted ('OK', 'Yes', 'Confirm', etc) and no
exception raised but a detectable warning made available
= 'dismiss': all alerts are dismissed ('No', 'Cancel', close) and no
exception raised but a detectable warning made available
= 'ignore': not sure how this is differ from 'dismiss' but should not raise
an exception.
= 'manual': raises the exception, leaves the alert, and gives control to
the script to catch and handle the exception.

Perhaps some use cases need the alerts to be discarded, but certainly not
automated testing situations where some alerts _are_ expected.

[sele...@googlecode.com]

Comment #43 on issue 3392 by patr...@3qilabs.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

This is definately a show-stopper.
Even more so if the current behavior propogates to the FF and IE drivers.

I concur with @edmund.pa...

We need to be able to decide how to handle an alert/confirmation each time

[sele...@googlecode.com]

Comment #44 on issue 3392 by barancev: Allow capability to specify

auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Re: #43: You can use driver.switchTo().alert().accept() or
driver.switchTo().alert().dismiss() to handle *expected* alerts.

[sele...@googlecode.com]

Comment #45 on issue 3392 by patr...@3qilabs.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

barancev,
Thank you. I'll give those a try, assuming it can be set on the fly.

Is the alert still intercepted and not shown? Still need to be able to
check the text in some cases to make sure it is actually the expected alert
and not something else, or where accept/dismiss depends on the content of
the alert.

[sele...@googlecode.com]

Comment #46 on issue 3392 by patr...@3qilabs.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Have a question that am unable to find answer in extensive google searches:
Is the 'unexpectedAlertBehaviour' capability settable in ChromeDriver and
Firefox as well as IEDriverServer?

Also where might I find ruby examples?

(I will post this in StackOverflow as well...)

[sele...@googlecode.com]

Comment #47 on issue 3392 by barancev: Allow capability to specify

auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Chrome -- no
Firefox -- yes
IE -- yes

[sele...@googlecode.com]

Comment #48 on issue 3392 by jfa...@gmail.com: Allow capability to specify

auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Barancev ... What bindings are you referring to when you say yes for IE?

Also anyone have any luck finding an example how to switch the alert
handling default capability in Ruby? I believe last I checked this was not
possible in the ruby bindings. Has that changed?

[sele...@googlecode.com]

Comment #49 on issue 3392 by barancev: Allow capability to specify

auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Any binding allows to set capabilities. You can find the list of supported
capabilities here:
https://code.google.com/p/selenium/wiki/DesiredCapabilities

[sele...@googlecode.com]

Comment #50 on issue 3392 by patr...@3qilabs.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Has anyone seen Ruby bindings examples of setting those DesiredCapabilities?

I have spent too many hours searching and either am blindered or this
really isn't possible...

[sele...@googlecode.com]

Comment #51 on issue 3392 by patr...@3qilabs.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Necessity required that I figure out answer to my own question (#50):

caps = Selenium::WebDriver::Remote::Capabilities.internet_explorer(
:unexpectedAlertBehaviour => 'ignore'
)
@browser = Watir::Browser.new(:ie, :desired_capabilities => caps)

[sele...@googlecode.com]

Comment #52 on issue 3392 by patr...@3qilabs.com: Allow capability to

specify auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

Necessity required me to figure out the answer to my own question (#50)

caps = Selenium::WebDriver::Remote::Capabilities.internet_explorer(
:unexpectedAlertBehaviour => 'ignore'
)

browser = Watir::Browser.new(:ie, :desired_capabilities => caps)

Works like a charm.

[sele...@googlecode.com]

Updates:
Status: Fixed
Labels: -Browser-Chrome

Comment #53 on issue 3392 by barancev: Allow capability to specify

auto-dismiss behaviour on UnhandledAlertException
http://code.google.com/p/selenium/issues/detail?id=3392

I'm closing the issue because it is implemented in all the browsers
supported by Selenium team. If someone wants to speed up implementing this
feature in chromedriver can either raise an issue in the chromedriver
tracker [1] or even help with patches.

[1] https://code.google.com/p/chromedriver/issues/list