Skip to content
This repository has been archived by the owner. It is now read-only.

ChromeDriver hangs on image click #1191

Closed
lukeis opened this Issue Mar 2, 2016 · 2 comments

Comments

Projects
None yet
1 participant
@lukeis
Copy link
Member

commented Mar 2, 2016

Originally reported on Google Code with ID 1191

Hi All,

I have an issue where the ChromeDriver hangs when 'clicking' an image that pops up
an alert. The firefox driver works fine.

What steps will reproduce the problem?
1. Load a page
2. Click image that pops up an alert

What is the expected output? What do you see instead?
Expected:
1) The alert pops up
2) Code (below) returns and execution continues
What happens:
1) the alert pops up
2) the click() call doesn't return (stack trace below)

What version of the product are you using? On what operating system?
This is on Ubuntu Linux 10.10 and 9.04, both using gnome. Tried with both Google Chrome
and Chromium (both 8.0.552.224). The Selenium version is 2.0b1.


Please provide any additional information below.
Code sample (with line numbers):
49      // === Delete contact
50      WebElement deleteImage = driver.findElement(By.xpath("//tr[td/. = '" + GROUP_NAME
+ "']//img"));
51      deleteImage.click();
52      Alert alert = driver.switchTo().alert();
53      alert.accept();

The call to deleteImage.click() doesn't return.
StackTrace:
Thread [main] (Suspended)   
    SubProcess.exitValue() line: 85 
    SubProcess.isRunning() line: 102    
    ChromeBinary.isRunning() line: 166  
    ChromeCommandExecutor.getOldestSocket() line: 348   
    ChromeCommandExecutor.handleResponse() line: 314    
    ChromeCommandExecutor.execute(Command) line: 187    
    ChromeDriver(RemoteWebDriver).execute(String, Map<String,?>) line: 379  
    ChromeDriver.execute(String, Map<String,?>) line: 85    
    ChromeWebElement(RemoteWebElement).execute(String, Map<String,?>) line: 235 
    ChromeWebElement(RemoteWebElement).click() line: 62 
    TestManageContactGroups.testContactGroupsManagement() line: 51  
    NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native
method] 
    NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39  
    DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25  
    Method.invoke(Object, Object...) line: 597  
    TestManageContactGroups(TestCase).runTest() line: 168   
    TestManageContactGroups(TestCase).runBare() line: 134   
    TestResult$1.protect() line: 110    
    TestResult.runProtected(Test, Protectable) line: 128    
    TestResult.run(TestCase) line: 113  
    TestManageContactGroups(TestCase).run(TestResult) line: 124 
    TestSuite.runTest(Test, TestResult) line: 232   
    TestSuite.run(TestResult) line: 227 
    JUnit38ClassRunner.run(RunNotifier) line: 83    
    JUnit4TestMethodReference(JUnit4TestReference).run(TestExecution) line: 49  
    TestExecution.run(ITestReference[]) line: 38    
    RemoteTestRunner.runTests(String[], String, TestExecution) line: 467    
    RemoteTestRunner.runTests(TestExecution) line: 683  
    RemoteTestRunner.run() line: 390    
    RemoteTestRunner.main(String[]) line: 197   





thanks for your help!
Marc

Reported by mrawji on 2011-01-12 22:43:03

@lukeis

This comment has been minimized.

Copy link
Member Author

commented Mar 2, 2016

Alert handling is only implemented in the FirefoxDriver at the moment.  Track issue
27 to find out when the ChromeDriver supports this.

Reported by dawagner on 2011-01-12 22:56:30

  • Status changed: Duplicate
  • Merged into: #27
@lukeis

This comment has been minimized.

Copy link
Member Author

commented Mar 2, 2016

Reported by luke.semerau on 2015-09-17 18:11:49

  • Labels added: Restrict-AddIssueComment-Commit

@lukeis lukeis closed this Mar 2, 2016

@SeleniumHQ SeleniumHQ locked and limited conversation to collaborators Mar 4, 2016

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.