Skip to content
This repository has been archived by the owner on Nov 29, 2018. It is now read-only.

Clicking with 2.12.0 using Firefox 5 sometimes works and sometimes does not #2864

Closed
lukeis opened this issue Mar 3, 2016 · 23 comments
Closed

Comments

@lukeis
Copy link
Member

lukeis commented Mar 3, 2016

Originally reported on Google Code with ID 2864

This may be related to what is discussed in issue 1989.  I am hoping that the example
HTML code may help in trying to track down why it is failing in some cases and not
in others.

Selenium version: 2.12.0
OS: Windows XP & Vista
Browser: Firefox
Browser version: 5.0.1

I have two pages where I am configuring preferences before going into the real tests.
 The act of setting the preferences is another test case that the others all depend
on (otherwise the tests would be invalid).  Note I am using WebDriverBackedSelenium
for my code.

On both pages there is an 'Apply' button I click to apply the settings.  The first
page works and the second does not.

Here is the HTML for the first one:
<input type="Submit" onclick="return checkForm();" value="Apply" name="ViewingOptions">

I do a selenium.click("//input[@value='Apply']") and this works.

Here is the HTML for the second one:
<input type="Submit" value="Apply" name="Submit">

Originally I was using the same locator string for the selenium.click(), but I changed
it to be "//input[@name='Submit']" and still got the same results.  So I changed the
code to use WebDriver:
driver.findElementByName("Submit").click();

Still the exact same failure message.  Note that I do see the element being selected
prior to the exception being thrown, so it is obvious that the locator is working,
which the error message would seem to indicate as well.

Finally I changed it to:
driver.findElementByName("Submit").sendKeys("\r");

That worked!  This is seriously broken if the click() functions only
work randomly on buttons.  Previously I was using 2.5.0 and having no
such problems, but I am not sure if I ran this under 2.12.0 without error after I switched
to it on Monday or not.  I did switch back briefly to 2.5.0 and I am still getting
the same error, so this is not a regression in 2.12.0.  It is entirely possible some
minor change was done to the page where it is failing.

The stack trace when it fails is this (I am running on XP and the
remote server and grid server are on Vista):
com.thoughtworks.selenium.SeleniumException: [Exception... "Component
returned failure code: 0x80004005 (NS_ERROR_FAILURE)
[nsINativeEvents.click]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"
location: "JS frame ::
file:///C:/Users/mriley/AppData/Local/Temp/anonymous4563302850717977356webdriver-profile/extensions/fxdri...@googlecode.com/components/driver-component.js
->
file:///C:/Users/mriley/AppData/Local/Temp/anonymous4563302850717977356webdriver-profile/extensions/fxdri...@googlecode.com/components/wrappedElement.js
:: <TOP_LEVEL> :: line 107"  data: no]; duration or timeout: 1.53 seconds
Build info: version: '2.12.0', revision: '14666', time: '2011-11-10 18:35:23'
System info: os.name: 'Windows Vista', os.arch: 'x86', os.version: '6.0', java.version:
'1.6.0_29'
Driver info: driver.version: RemoteWebDriver; duration or timeout: 1.83 seconds
Build info: version: '2.12.0', revision: '14666', time: '2011-11-10 18:36:18'
System info: os.name: 'Windows XP', os.arch: 'x86', os.version:  5.1', java.version:
'1.6.0_26'
Driver info: driver.version: RemoteWebDriver
        at
org.openqa.selenium.internal.seleniumemulation.SeleneseCommand.apply(SeleneseCommand.java:42)
        at
org.openqa.selenium.internal.seleniumemulation.Timer.run(Timer.java:39)
        at
org.openqa.selenium.WebDriverCommandProcessor.execute(WebDriverCommandProcessor.java:265)
        at
org.openqa.selenium.WebDriverCommandProcessor.doCommand(WebDriverCommandProcessor.java:195)
        at
com.thoughtworks.selenium.DefaultSelenium.click(DefaultSelenium.java:
186)

Reported by lvskiprof on 2011-11-17 16:53:21

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

Reported by barancev on 2011-11-18 12:18:17

  • Labels added: Component-WebDriverBackedSelenium, Browser-IE

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

Seeing this in 2.13 with FF 8.0 also. I pretty much had to code around it, using driver.findElement(By.xpath(xpath)).sendKeys()
etc.


Reported by ceakins on 2011-11-22 19:40:36

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

@lvskiprof: Could you try to run the same test with 2.13? There was a change in wrappedElement.js
that can be related to this issue (see r14704)

@ceakins: I see your comment about 2.13 but I want to make sure that it is the same
issue, not an another one with similar symptoms.

Reported by barancev on 2011-11-22 20:43:08

  • Status changed: NeedsClarification
  • Labels added: Browser-Firefox
  • Labels removed: Browser-IE

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

12:11:59.794 INFO - driver.findElement("By.xpath: //input[@id='filterSubmit']")
12:11:59.913 ERROR - Class: <INTERNAL CLASS HIDDEN> Threw Exception: org.openqa.selenium.InvalidElementStateException:
[Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsINativeEvents.click]"
 nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: file:///C:/Windows/TEMP/anonymous4665590146838981241webdriver-profile/extensions/fxdriver@googlecode.com/components/driver-component.js
-> file:///C:/Windows/TEMP/anonymous4665590146838981241webdriver-profile/extensions/fxdriver@googlecode.com/components/wrappedElement.js
:: <TOP_LEVEL> :: line 108"  data: no]; duration or timeout: 112 milliseconds

The test this runs in is actually a suite of tests we use for build verification I
wrote.  So in this instance it's in a while loop waiting for an element to show up,
and so it clicks a button every 30 seconds to refresh this page. It's a filter on the
page and expecting a list item to show up based on the search criteria. It breaks out
of the loop when it reaches a certain time. It seems to happen randomly, it doesn't
always happen. Hope that helps. I had to hide my class name.

Reported by ceakins on 2011-11-23 00:01:40

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

Forgot the rest of it:
Build info: version: 'unknown', revision: 'unknown', time: 'unknown'
System info: os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version:
'1.6.0_21'
Driver info: driver.version: RemoteWebDriver

Reported by ceakins on 2011-11-23 00:09:04

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

Stack:
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
    at java.lang.reflect.Constructor.newInstance(Unknown Source)
    at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:147)
    at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:113)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:416)
    at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:231)
    at org.openqa.selenium.remote.RemoteWebElement.click(RemoteWebElement.java:72)
    at com.allstardirectories.test.common.WebDriverUtils.clickLink(Unknown Source)
    at com.allstardirectories.test.bvt.LeadCheck.checkLead(Unknown Source)
    at com.allstardirectories.test.bvt.ExecuteBVT.testExecuteBvt(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
    at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
    at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
    at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
    at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
    at org.junit.runner.JUnitCore.run(JUnitCore.java:157)
    at org.junit.runner.JUnitCore.run(JUnitCore.java:136)
    at com.segue.tm.plugins.testlaunch.junit.ju4support.JU4Helper.executeJunitTest(JU4Helper.java:99)
    at com.segue.tm.plugins.testlaunch.junit.ju4support.JU4Helper.executeJU4TestClassOrMethodOnly(JU4Helper.java:54)
    at com.segue.tm.plugins.testlaunch.junit.ju4support.JUnit4CmdLineWrapper.executeTestClassOrMethod(JUnit4CmdLineWrapper.java:47)
    at com.segue.tm.plugins.testlaunch.junit.ju4support.JUnit4CmdLineWrapper.main(JUnit4CmdLineWrapper.java:81)
Caused by: org.openqa.selenium.remote.ErrorHandler$UnknownServerException: [Exception...
"Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsINativeEvents.click]"
 nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: file:///C:/Windows/TEMP/anonymous272490435440013205webdriver-profile/extensions/fxdriver@googlecode.com/components/driver-component.js
-> file:///C:/Windows/TEMP/anonymous272490435440013205webdriver-profile/extensions/fxdriver@googlecode.com/components/wrappedElement.js
:: <TOP_LEVEL> :: line 108"  data: no]
Build info: version: 'unknown', revision: 'unknown', time: 'unknown'
System info: os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version:
'1.6.0_21'
Driver info: driver.version: unknown
    at <anonymous class>.<anonymous method>(file:///C:/Windows/TEMP/anonymous272490435440013205webdriver-profile/extensions/fxdriver@googlecode.com/components/driver-component.js
-> file:///C:/Windows/TEMP/anonymous272490435440013205webdriver-profile/extensions/fxdriver@googlecode.com/components/wrappedElement.js:126)
    at <anonymous class>.<anonymous method>(file:///C:/Windows/TEMP/anonymous272490435440013205webdriver-profile/extensions/fxdriver@googlecode.com/components/nsCommandProcessor.js:306)
    at <anonymous class>.<anonymous method>(file:///C:/Windows/TEMP/anonymous272490435440013205webdriver-profile/extensions/fxdriver@googlecode.com/components/nsCommandProcessor.js:320)
    at <anonymous class>.<anonymous method>(file:///C:/Windows/TEMP/anonymous272490435440013205webdriver-profile/extensions/fxdriver@googlecode.com/components/nsCommandProcessor.js:197)


Reported by ceakins on 2011-11-23 00:11:08

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

I just tried 2.13.0 and I am still getting the same failure:

com.thoughtworks.selenium.SeleniumException: [Exception... "Component returned failure
code: 0x80004005 (NS_ERROR_FAILURE) [nsINativeEvents.click]"  nsresult: "0x80004005
(NS_ERROR_FAILURE)"  location: "JS frame :: file:///C:/Users/mriley/AppData/Local/Temp/anonymous2668221769154936974webdriver-profile/extensions/fxdriver@googlecode.com/components/driver-component.js
-> file:///C:/Users/mriley/AppData/Local/Temp/anonymous2668221769154936974webdriver-profile/extensions/fxdriver@googlecode.com/components/wrappedElement.js
:: <TOP_LEVEL> :: line 108"  data: no]; duration or timeout: 1.49 seconds
Build info: version: '2.13.0', revision: '14793', time: '2011-11-18 13:16:47'
System info: os.name: 'Windows Vista', os.arch: 'x86', os.version: '6.0', java.version:
'1.6.0_29'
Driver info: driver.version: RemoteWebDriver; duration or timeout: 2.27 seconds
Build info: version: '2.13.0', revision: '14793', time: '2011-11-18 13:17:39'
System info: os.name: 'Windows XP', os.arch: 'x86', os.version: '5.1', java.version:
'1.6.0_26'
Driver info: driver.version: RemoteWebDriver
    at org.openqa.selenium.internal.seleniumemulation.SeleneseCommand.apply(SeleneseCommand.java:42)
    at org.openqa.selenium.internal.seleniumemulation.Timer.run(Timer.java:39)
    at org.openqa.selenium.WebDriverCommandProcessor.execute(WebDriverCommandProcessor.java:265)
    at org.openqa.selenium.WebDriverCommandProcessor.doCommand(WebDriverCommandProcessor.java:195)
    at com.thoughtworks.selenium.DefaultSelenium.click(DefaultSelenium.java:186)
    at current.Current.testDOTN_CUR_VT_Prereq(Current.java:275)

Reported by lvskiprof on 2011-11-23 22:26:51

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

1. The InternetExplorerDriver also has this problem
2. Clicking twice on the element also works, that is: element.click(); element.click();
3. Because sometimes the first click works, and if the click causes a new page to be
loaded the element becomes stale and any further click is invalid, it is better to
write:
element.click(); try { element.click(); } catch (StaleElementReferenceException e)
{ }
4. If you are afraid that two clicks might not be enough, wrap the code in an ExpectedCondition
(but, as I learned some hours ago from a Selenium developer, you are not allowed to
used implicit waits anymore):
new WebDriverWait(webDriver, TIMEOUT).until(new ExpectedCondition<Boolean>() { public
Boolean apply(WebDriver driver) { element.click(); return ExpectedConditions.stalenessOf(element).apply(driver);
} }
5. By now, the tests don't test anymore if something happens when you click on some
element, but if something eventually happens if you click enough on the element (which
is definitely not the same thing)
6. You can also use the WebDriverWait-trick for things like "repeat { click } until
the checkbox is checked" or "repeat { select the item in the combo box } until the
item is selected" and so on.

Reported by clovis.seragiotto@raibau.at on 2011-11-30 09:25:00

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

I am having similar problems.  Clicks that were working on Selenium 2.5 with Firefox
7 with the C# API produce no result on Selenium 2.12 or 2.14.  However, I do not see
any error messages - just no response in the web browser.  It takes a whole bunch of
clicks before anything happens.

The HTML for one of the elements I'm trying to click looks like this:

<div class="dijitTab" lang="" dojoattachevent="onclick:onClick" dojoattachpoint="titleNode"
role="presentation" dir="" widgetid="gbAuthorToolsTabContainer_tablist_addContent">
<div class="dijitTabInnerDiv" dojoattachpoint="innerDiv" role="presentation">
<div class="dijitTabContent" dojoattachpoint="tabContent" role="presentation">
<div id="gbAuthorToolsTabContainer_tablist_addContent" dojoattachpoint="focusNode"
role="tab" style="-moz-user-select: none;" tabindex="-1" title="" aria-selected="false">
<img class="dijitIcon dijitTabButtonIcon dijitNoIcon" dojoattachpoint="iconNode" alt=""
src="http://static.ecollege.com/dojo/1.6.1/dojo/resources/blank.gif">
<span class="tabLabel" dojoattachpoint="containerNode" style="-moz-user-select: none;">Add</span>
<span class="dijitInline dijitTabCloseButton dijitTabCloseIcon" role="presentation"
dojoattachevent="onclick: onClickCloseButton" dojoattachpoint="closeNode" style="display:
none;">
</div>
</div>
</div>
</div>

I'm using Find.Element(By.Xpath(locatorString)), where locatorString = "//div[@id='gbAuthorToolsTabContainer_tablist_addContent'
and @aria-selected='false']/span"

Webdriver seems to be finding the element and indicates that it's visible, and it looks
to my script like the clicks are succeeding - but it takes a bunch of times before
anything happens.

Reported by LordOfTheBrambles on 2011-12-08 19:39:18

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

Hi! I have 100% the same problem on Selenium 2.15.0 , it reproduces in Windows XP SP3,
FF 8.0.1, But I can't reproduce the same on MacOS X 10.7.2 FF 8.0.1

  self.wait_for_action(self.driver.find_element_by_xpath("//input[@value='%s']" % name).click())
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/selenium/webdriver/remote/webelement.py",
line 45, in click
    self._execute(Command.CLICK_ELEMENT)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/selenium/webdriver/remote/webelement.py",
line 194, in _execute
    return self._parent.execute(command, params)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/selenium/webdriver/remote/webdriver.py",
line 153, in execute
    self.error_handler.check_response(response)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/selenium/webdriver/remote/errorhandler.py",
line 147, in check_response
    raise exception_class(message, screen, stacktrace)
WebDriverException: Message: u'[Exception... "Component returned failure code: 0x80004005
(NS_ERROR_FAILURE) [nsINativeEvents.click]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"
 location: "JS frame :: file:///C:/DOCUME~1/maven/LOCALS~1/Temp/anonymous4506784057084087892webdriver-profile/extensions/fxdriver@googlecode.com/components/driver-component.js
-> file:///C:/DOCUME~1/maven/LOCALS~1/Temp/anonymous4506784057084087892webdriver-profile/extensions/fxdriver@googlecode.com/components/wrappedElement.js
:: <TOP_LEVEL> :: line 124"  data: no]\nCommand duration or timeout: 1.28 seconds\nBuild
info: version: \'2.15.0\', revision: \'15105\', time: \'2011-12-08 09:56:25\'\nSystem
info: os.name: \'Windows XP\', os.arch: \'x86\', os.version: \'5.1\', java.version:
\'1.6.0_25\'\nDriver info: driver.version: RemoteWebDriver' ; Screenshot: available
via screen ; Stacktrace: Method newInstance0 threw an error in None 

Reported by strazhnyk on 2011-12-14 14:39:35

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

This issue reproduces when previously, there is a select like this self.driver.find_element_by_id(item).click()
after self.driver.find_element_by_id(item).send_keys(value). Now you should be able
to select an option by clicking on it without clicking the parent select. (that's according
to Simon Stewart, and it works for me as well)

Reported by strazhnyk on 2011-12-14 16:46:56

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

I'm able to reproduce it on Windows 7 but not on Ubuntu 10.10

Reported by alejandrozalazar on 2011-12-20 20:59:47

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

When exception like this is caused by "[nsINativeEvents.click]" in FirefoxDriver, one
of the workarounds is to disable native events by initializing FirefoxDriver using
the following code:

FirefoxProfile profile = new FirefoxProfile();
profile.setEnableNativeEvents(false);
drv=new FirefoxDriver(profile);

Reported by mindfr3aq on 2012-01-17 15:36:01

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

I'm running Win7 IE9 and use Selenium 2.20 in a Java (1.7) Eclipse-Environment (and
I am quite new to all this ;) )

My Workflow-Test works fine with FirefoxDriver (LoginPage: sendKeys(username), sendKeys(password)
submit()) goes on to the next PageObject and so on.
The button is really as simple as this: 
<input type="submit" value="Anmelden" name="action">
and I do a  driver.findElement(By.name("action").submit();
Changing the WebDriver to InternetExplorerDriver keeps me on the LoginPage with a blue
border around my "Anmelden"-Button and nothing happens any more.

If I debug the Workflow and click the button manually after highlighting, the process
continues until the next click on a Button / Link is neccessary.

Most of our customers use IE so it is really important, tests can be processed with
IE.

Reported by samiira.cat on 2012-04-26 10:57:50

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

Setting

profile.setEnableNativeEvents(false)

worked for me
Thx

Reported by paul.bernet on 2013-01-08 13:35:32

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

This has continued to occur in 2.31.0, though I have been working mostly in IE.


Reported by karisvanvalin@yahoo.com on 2013-04-05 13:48:14

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

I have just seen this in 2.33.0 as well, on a seemingly-innocuous line like this:

  selenium.click("css=input#billingZipCode");

The strange thing is that it works if I run it locally, but not if I run it through
a selenium grid machine.

Platform info and stack trace below:

org.openqa.selenium.WebDriverException: Component returned failure code: 0x80004005
(NS_ERROR_FAILURE) [nsINativeMouse.click]
Build info: version: '2.33.0', revision: '4e90c97', time: '2013-05-22 15:32:38'
System info: os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version:
'1.7.0_25'
Driver info: driver.version: unknown
Command duration or timeout: 16 milliseconds
Build info: version: '2.33.0', revision: '4e90c97', time: '2013-05-22 15:32:38'
System info: os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.18-348.1.1.el5',
java.version: '1.7.0_02'
Session ID: ac1fafee-8d78-4f16-8461-a51576056da3
Driver info: org.openqa.selenium.remote.RemoteWebDriver
Capabilities [{platform=XP, javascriptEnabled=true, acceptSslCerts=true, browserName=firefox,
rotatable=false, locationContextEnabled=true, webdriver.remote.sessionid=ac1fafee-8d78-4f16-8461-a51576056da3,
version=17.0.8, databaseEnabled=true, cssSelectorsEnabled=true, handlesAlerts=true,
browserConnectionEnabled=true, webStorageEnabled=true, nativeEvents=true, applicationCacheEnabled=true,
takesScreenshot=true}]
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
    at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:191)
    at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:145)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:554)
    at org.openqa.selenium.remote.RemoteExecuteMethod.execute(RemoteExecuteMethod.java:34)
    at org.openqa.selenium.remote.RemoteMouse.click(RemoteMouse.java:58)
    at org.openqa.selenium.interactions.ClickAction.perform(ClickAction.java:34)
    at org.openqa.selenium.interactions.CompositeAction.perform(CompositeAction.java:31)
        at com.myplace.MyClass.testClicking(MyClass.java:1337)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:601)
    at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
    at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
    at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
    at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
    at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
    at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
    at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: org.openqa.selenium.remote.ErrorHandler$UnknownServerException: Component
returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsINativeMouse.click]
Build info: version: '2.33.0', revision: '4e90c97', time: '2013-05-22 15:32:38'
System info: os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version:
'1.7.0_25'
Driver info: driver.version: unknown
Build info: version: '2.33.0', revision: '4e90c97', time: '2013-05-22 15:32:38'
System info: os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.18-348.1.1.el5',
java.version: '1.7.0_02'
Driver info: driver.version: unknown


Reported by dceddia on 2013-09-27 12:22:09

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

More info from #18... this particular test's failure mode looks something like:

        1. Click a <select> element, which causes a drop down.
        2. Verify the text of a tooltip that appears
fail->  3. Click an <input> element that is currently obscured by the <select>'s dropdown.

Strange thing is this works fine on Firefox 17.0.6 linux, but (usually) not on Firefox
17.0.8 windows.

Reported by dceddia on 2013-09-27 12:56:16

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

And a little more info: It does not seem to matter whether the <select> dropdown obscures
another input or not -- while that dropdown is visible, clicking any other <input>
or even clicking the <select> itself causes this error.

So far, the suggestion provided earlier (profile.setEnableNativeEvents(false)) is the
only way I've found to eliminate this error.

Reported by dceddia on 2013-09-27 13:51:03

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

I'm going to close this issue because there is no reproduction scenario here.
If someone can provide a sample page where the issue occurs please do.

Reported by barancev on 2013-10-02 20:09:36

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

Closing the issue due to miss of reproduction scenario.

Reported by barancev on 2013-10-17 18:51:59

  • Status changed: Invalid

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

thank you mindfr...@gmail.com

Reported by rcaballero@conexia.com on 2015-02-02 22:35:29

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

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

  • Labels added: Restrict-AddIssueComment-Commit

@lukeis lukeis closed this as completed Mar 3, 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.
Projects
None yet
Development

No branches or pull requests

1 participant