Issue metadata
Sign in to add a comment
|
ChromeDriver no longer throws UnhandledAlertException on system alerts
Reported by
john...@gmail.com,
Jul 27 2016
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.82 Safari/537.36 Steps to reproduce the problem: 1. Run a Selenium test which causes a system alert to be displayed (ChromeDriver 2.19.0.0) 2. previous version used to report an UnhandledAlertException, which could be caught and handled 3. Current version does not throw exceptions, which causes test execution to stop What is the expected behavior? UnhandledAlertException should be thrown. What went wrong? A system alert was displayed, but the UnhandledAlertException was not thrown by ChromeDriver (2.19.0.0) Did this work before? Yes Not exactly sure - may have been 51.0.2704. Should have recorded the delta... Chrome version: 52.0.2743.82 Channel: stable OS Version: 6.3 Flash Version: Shockwave Flash 22.0 r0
,
Jul 27 2016
Updating to ChromeDriver 2.22 and Selenium WebDriver 2.53.1 appears to have solved this issue. Now to get rid of the "developer mode extensions" pop-up...
,
Jul 28 2016
,
Jul 28 2016
ChromeOptions options = new ChromeOptions();
options.AddArguments("--disable-extensions");
options.AddArguments("no-sandbox");
driver = new ChromeDriver(options);
Gets ride of developer mode extensions.
,
Jul 29 2016
,
Aug 5 2016
I have the same issue with Selenium (2.53.1) and ChromeDriver 2.22 and 2.23. ChromeDriver 2.22 is worse because then I get the "developer mode extension warning."
,
Aug 22 2016
Selenium 2.53.1 and ChromeDriver 2.22 did fix the issue for me. However, it was hard to tell that webdriver-manager was running the right versions. Even after updating both softwares, you still must specify the version to run with: ``` webdriver-manager start --versions.standalone="2.53.1" --versions.chrome="2.22" ```
,
Nov 17 2016
Original issue of 'UnhandledAlertException not being thrown' is no longer reproducible on the latest Chrome v54.0.2840.100 and Chromedriver v2.25 'developer mode extensions' pop up issue was fixed in http://crrev.com/596ca47395e0ead2693f84c2483446627c29960e. More details at issue chromedriver:1460 Closing this issue. Please feel free to file a new bug if you encounter any problem in Chromedriver. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by john...@gmail.com
, Jul 27 2016