Element is not currently visible and so may not be interacted with selenium-webdriver (2.32.1)

SeleniumHQ / selenium-google-code-issue-archive

Archive, please see main selenium repo

https://github.com/seleniumhq/selenium

346 stars 194 forks source link

Element is not currently visible and so may not be interacted with selenium-webdriver (2.32.1) #5557

Closed lukeis closed 8 years ago

lukeis commented 8 years ago

Originally reported on Google Code with ID 5557


What steps will reproduce the problem?
1.selenium-webdriver (2.32.1)

What is the expected output? What do you see instead?
Should be able to enter text in the search text field
      Element is not currently visible and so may not be interacted with (Selenium::WebDriver::Error::ElementNotVisibleError)

Selenium version: 2.32.1
OS: Windows 
Browser: Firefox
Browser version: 20.0.1

Failing step :
 enters "dress" on the text field

Stack Trace :

      Element is not currently visible and so may not be interacted with (Seleni
um::WebDriver::Error::ElementNotVisibleError)
      [remote server] file:///C:/Users/abc/AppData/Local/Temp/webdriver-profile20130425-4520-5frx0k/extensions/fxdriver@googlecode.com/components/command_p
rocessor.js:10402:in `DelayedCommand.prototype.checkPreconditions_'
      [remote server] file:///C:/Users/abc/AppData/Local/Temp/webdriver-profile20130425-4520-5frx0k/extensions/fxdriver@googlecode.com/components/command_p
rocessor.js:10421:in `DelayedCommand.prototype.executeInternal_/h'     [remote server]
file:///C:/Users/abc/AppData/Local/Temp/webdriver-profile20130425-4520-5frx0k/extensions/fxdriver@googlecode.com/componentscommand_p
rocessor.js:10426:in `DelayedCommand.prototype.executeInternal_'
      [remote server] file:///C:/Users/abc/AppData/Local/Temp/webdriver-profile20130425-4520-5frx0k/extensions/fxdriver@googlecode.com/components/command_p
rocessor.js:10366:in `DelayedCommand.prototype.execute/<'(eval):1:in `process_watir_call'

Reported by watirwebdriver123 on 2013-04-25 14:47:39

lukeis commented 8 years ago

Please provide a sample page to reproduce the issue.

Reported by barancev on 2013-04-28 19:15:16

Status changed: NeedsClarification
Labels added: Browser-Firefox

lukeis commented 8 years ago

I'm also encountering this issue. This happens in versions 2.32.0 and above, but does
not occur in versions 2.31.2 and below.

With Selenium 2.32.0, the Firefox version doesn't seem to matter. This issue happens
with all versions I've tried - 18, 19, and 20.

Finding an element with the same line of code gives a different result depending on
the Selenium version. "Displayed" is false in 2.32.0 and true in 2.31.2.

code to find the element (C#): driver.FindElement(By.CssSelector("div.x-grid3-col-timer
div.stopwatchBtn a"));

result in 2.32.0:
{OpenQA.Selenium.Firefox.FirefoxWebElement}
    [OpenQA.Selenium.Firefox.FirefoxWebElement]: {OpenQA.Selenium.Firefox.FirefoxWebElement}
    Displayed: false
    Enabled: true
    Location: {X = 907 Y = 282}
    Selected: false
    Size: {Width = 42 Height = 23}
    TagName: "a"
    Text: ""

result in 2.31.2:
{OpenQA.Selenium.Firefox.FirefoxWebElement}
    [OpenQA.Selenium.Firefox.FirefoxWebElement]: {OpenQA.Selenium.Firefox.FirefoxWebElement}
    Displayed: true
    Enabled: true
    Location: {X = 907 Y = 282}
    Selected: false
    Size: {Width = 42 Height = 23}
    TagName: "a"
    Text: ""

page details:
I can't directly link to the page in question, since it requires logging in as a user
of clicktime.com

The element I'm trying to click is defined by this bit of HTML:
<td class="x-grid3-col x-grid3-cell x-grid3-td-timer " tabindex="0" style="width: 98px;">
    <div class="x-grid3-cell-inner x-grid3-col-timer" unselectable="on">
        <div class="stopwatchBtn ">
            <a>
                <span></span>
            </a>
        </div>
    </div>
</td>

Here's the CSS. It specifies "display" as "block", which should be visible:
.stopwatchBtn a {
    background-image: url("/images/stopwatchidle.png");
    background-repeat: no-repeat;
    display: block;
    height: 23px;
    position: absolute;
    width: 42px;
}

What changed in how Selenium determines if an element is displayed?

Reported by audrey.penven on 2013-05-01 22:58:34

lukeis commented 8 years ago

I'm also facing the same problem. When ever we get new webdriver, it fails some of the
scripts related to clicking on the Ul/li elements.

Reported by smitha.vummethala on 2013-05-10 17:09:13

lukeis commented 8 years ago

audrey.penven, smitha.vummethala: How can you guys say for sure you have *same* issue?
If you see Windows dialog "application has performed illegal operation" do you think
*all* operations has *same* bug?

Please raise a new issue, and provide a reproducible scenario and a *complete* sample
page with all relevant CSS and JS code that can affect visibility. A scenario that
uses a test accong to your real applicsation is acceptable too.

Reported by barancev on 2013-05-10 19:28:25

lukeis commented 8 years ago

     I am having trouble with with this in FireFox.  We're testing a GWT/GXT application
using selenium2library in Robot Framework.  Our application has embedded lists and
if one of the elements is not visible, then Click Element returns the error:

ElementNotVisibleException: Message: u'Element is not currently visible and so may
not be interacted with' ; Stacktrace: 
    at fxdriver.preconditions.visible (file:///var/folders/qk/6n3ttg097wlc9sqyrcw0q5fh0000gp/T/tmp7kn5tj/webdriver-py-profilecopy/extensions/fxdriver@googlecode.com/components/command_processor.js:7736)
    at DelayedCommand.prototype.checkPreconditions_ (file:///var/folders/qk/6n3ttg097wlc9sqyrcw0q5fh0000gp/T/tmp7kn5tj/webdriver-py-profilecopy/extensions/fxdriver@googlecode.com/components/command_processor.js:10437)
    at DelayedCommand.prototype.executeInternal_/h (file:///var/folders/qk/6n3ttg097wlc9sqyrcw0q5fh0000gp/T/tmp7kn5tj/webdriver-py-profilecopy/extensions/fxdriver@googlecode.com/components/command_processor.js:10456)
    at DelayedCommand.prototype.executeInternal_ (file:///var/folders/qk/6n3ttg097wlc9sqyrcw0q5fh0000gp/T/tmp7kn5tj/webdriver-py-profilecopy/extensions/fxdriver@googlecode.com/components/command_processor.js:10461)
    at DelayedCommand.prototype.execute/< (file:///var/folders/qk/6n3ttg097wlc9sqyrcw0q5fh0000gp/T/tmp7kn5tj/webdriver-py-profilecopy/extensions/fxdriver@googlecode.com/components/command_processor.js:10401)

This is only happening in FireFox.  The same tests in Chrome work like a charm.

I dummied up a simple test case that demonstrates the error.  This test uses the sencha.com/examples
site, from which we get the templates we use in our application.

*** Settings ***
Documentation     This is a test suite. 
Suite Teardown    Close All Browsers
Test Timeout      1 minute
Library           Selenium2Library    5s    run_on_failure=Capture Page Screenshot

*** Test Cases ***
Test1
    Open Browser    http://www.sencha.com/examples/    firefox
    Maximize Browser Window
    Comment    Expand tree items.
    Click Element    xpath=//span[text()='Windows']/../img[2]
    Click Element    xpath=//span[text()='TreeGrid']/../img[2]
    Click Element    xpath=//span[text()='Tree']/../img[2]
    Click Element    xpath=//span[text()='ToolBar & Menu']/../img[2]
    Click Element    xpath=//span[text()='Templates & Lists']/../img[2]
    Click Element    xpath=//span[text()='Tabs']/../img[2]
    Click Element    xpath=//span[text()='Misc']/../img[2]
    Wait Until Page Contains Element    xpath=//span[text()="MessageBox"]    30s
    Click Element    //span[text()="MessageBox"]
    Capture Page Screenshot
    Sleep    5s

Reported by rbovill on 2013-08-12 17:33:06

lukeis commented 8 years ago

@rbovill: Please raise a new issue

Reported by barancev on 2013-08-12 17:39:41

lukeis commented 8 years ago

Closing the issue as there is no reproduction case provided. Feel free to ask for reopening
if it still actual.

Reported by barancev on 2013-10-23 21:23:17

Status changed: Invalid

lukeis commented 8 years ago

I feel this is a valid issue , as I encounter it . 

Test Name:  TestLogin
Test FullName:  PPBot.Test.TestBase.TestLogin
Test Source:    c:\Users\Naveen\PrintPlace\PPBot\PPBot\Test\TestBase.cs : line 18
Test Outcome:   Failed
Test Duration:  0:00:27.6165232

Result Message: 
Test method PPBot.Test.TestBase.TestLogin threw exception: 
OpenQA.Selenium.NoSuchElementException: Unable to locate element: {"method":"xpath","selector":"//*/html/body/div/div/div[2]/div/div"}
Result StackTrace:  
at OpenQA.Selenium.Remote.RemoteWebDriver.UnpackAndThrowOnError(Response errorResponse)
in c:\Projects\WebDriver\trunk\dotnet\src\webdriver\Remote\RemoteWebDriver.cs:line
993
   at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute,
Dictionary`2 parameters) in c:\Projects\WebDriver\trunk\dotnet\src\webdriver\Remote\RemoteWebDriver.cs:line
846
   at OpenQA.Selenium.Remote.RemoteWebDriver.FindElement(String mechanism, String value)
in c:\Projects\WebDriver\trunk\dotnet\src\webdriver\Remote\RemoteWebDriver.cs:line
877
   at OpenQA.Selenium.Remote.RemoteWebDriver.FindElementByXPath(String xpath) in c:\Projects\WebDriver\trunk\dotnet\src\webdriver\Remote\RemoteWebDriver.cs:line
664
   at OpenQA.Selenium.By.<>c__DisplayClasse.<XPath>b__c(ISearchContext context) in
c:\Projects\WebDriver\trunk\dotnet\src\webdriver\By.cs:line 164
   at OpenQA.Selenium.By.FindElement(ISearchContext context) in c:\Projects\WebDriver\trunk\dotnet\src\webdriver\By.cs:line
306
   at OpenQA.Selenium.Remote.RemoteWebDriver.FindElement(By by) in c:\Projects\WebDriver\trunk\dotnet\src\webdriver\Remote\RemoteWebDriver.cs:line
330
   at PPBot.Test.TestBase.TestLogin() in c:\Users\Naveen\PrintPlace\PPBot\PPBot\Test\TestBase.cs:line
23

Reported by naveenb29 on 2013-10-25 01:38:43

Attachment: PageSource.docx

lukeis commented 8 years ago

@naveenb29:
1) First send a question to selenium user list [1] with appeal "please help me understand
why I get this error"
2) If it happens to be an issue in Selenium but not your code raise a new issue, don't
bit dead horse. And don't forget to provide a complete executable scenario and a sample
page to reproduce it.

Reported by barancev on 2013-10-25 06:19:49

lukeis commented 8 years ago

I am getting error "OpenQA.Selenium.ElementNotVisibleException : Element is not currently
visible and so may not be interacted with". Can someone please help me with this. This
is truly impeding me. Please find the below scenario and the screenshot for this problem.
This application is internal to our company.

I am trying to delete the created user. I could get the xpath of the element as well.

Reported by pratyushacherukuri on 2014-02-12 00:52:43

Attachment: Untitled.png

lukeis commented 8 years ago

I believe, that's a long time bug with Selenium Firefox, though this issue is getting
closed all the time. 

To confirm if that is bug, try running the same test in Chrome Driver. If that works
in Chrome Driver, but not in Firefox Driver, that would be a bug. 

Also, I couldn't find any workaround so far. For me, the issue happens with some dynamic
JavaScript dialogs, though, I can't provide exact steps unfortunately.

Reported by taleodor on 2014-02-12 04:00:59

lukeis commented 8 years ago

Thanks for your help.

Reported by pratyushacherukuri on 2014-02-12 19:39:42

lukeis commented 8 years ago

Same issue with 2.40 and no problem with chrome driver.

It looks like I have this issue with firefox when there is a need to scroll down to
see the link/button as if Firefox was saying the button is hidden because it's not
on the visible area...

org.openqa.selenium.ElementNotVisibleException: Element is not currently visible and
so may not be interacted with
Command duration or timeout: 9 milliseconds
Build info: version: '2.40.0', revision: 'fbe29a9', time: '2014-02-19 20:54:28'
System info: host: 'scips-HP-EliteBook-8560w', ip: '127.0.1.1', os.name: 'Linux', os.arch:
'amd64', os.version: '3.11.0-19-generic', java.version: '1.8.0'
Driver info: org.openqa.selenium.firefox.FirefoxDriver
Capabilities [{applicationCacheEnabled=true, rotatable=false, handlesAlerts=true, databaseEnabled=true,
version=28.0, platform=LINUX, browserConnectionEnabled=true, nativeEvents=false, acceptSslCerts=true,
webStorageEnabled=true, locationContextEnabled=true, browserName=firefox, takesScreenshot=true,
javascriptEnabled=true, cssSelectorsEnabled=true}]
Session ID: f606da8e-b541-4b1d-aa32-819319a21c1a
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:408)
    at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:193)
    at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:145)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:573)
    at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:268)
    at org.openqa.selenium.remote.RemoteWebElement.click(RemoteWebElement.java:79)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:483)
    at org.openqa.selenium.support.events.EventFiringWebDriver$EventFiringWebElement$1.invoke(EventFiringWebDriver.java:331)
    at com.sun.proxy.$Proxy3.click(Unknown Source)
    at org.openqa.selenium.support.events.EventFiringWebDriver$EventFiringWebElement.click(EventFiringWebDriver.java:344)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:483)
    at org.openqa.selenium.remote.server.KnownElements$1.invoke(KnownElements.java:63)
    at com.sun.proxy.$Proxy4.click(Unknown Source)
    at org.openqa.selenium.remote.server.handler.ClickElement.call(ClickElement.java:29)
    at org.openqa.selenium.remote.server.handler.ClickElement.call(ClickElement.java:1)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at org.openqa.selenium.remote.server.DefaultSession$1.run(DefaultSession.java:170)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:744)
Caused by: org.openqa.selenium.remote.ErrorHandler$UnknownServerException: Element
is not currently visible and so may not be interacted with
Build info: version: '2.40.0', revision: 'fbe29a9', time: '2014-02-19 20:54:28'
System info: host: 'scips-HP-EliteBook-8560w', ip: '127.0.1.1', os.name: 'Linux', os.arch:
'amd64', os.version: '3.11.0-19-generic', java.version: '1.8.0'
Driver info: driver.version: unknown
    at <anonymous class>.fxdriver.preconditions.visible(file:///tmp/anonymous7561919554867418931webdriver-profile/extensions/fxdriver@googlecode.com/components/command_processor.js:8225)
    at <anonymous class>.DelayedCommand.prototype.checkPreconditions_(file:///tmp/anonymous7561919554867418931webdriver-profile/extensions/fxdriver@googlecode.com/components/command_processor.js:10861)
    at <anonymous class>.DelayedCommand.prototype.executeInternal_/h(file:///tmp/anonymous7561919554867418931webdriver-profile/extensions/fxdriver@googlecode.com/components/command_processor.js:10878)
    at <anonymous class>.DelayedCommand.prototype.executeInternal_(file:///tmp/anonymous7561919554867418931webdriver-profile/extensions/fxdriver@googlecode.com/components/command_processor.js:10883)
    at <anonymous class>.DelayedCommand.prototype.execute/<(file:///tmp/anonymous7561919554867418931webdriver-profile/extensions/fxdriver@googlecode.com/components/command_processor.js:10825)
15:58:14.546 WARN - Exception: Element is not currently visible and so may not be interacted
with
Command duration or timeout: 9 milliseconds
Build info: version: '2.40.0', revision: 'fbe29a9', time: '2014-02-19 20:54:28'
System info: host: 'scips-HP-EliteBook-8560w', ip: '127.0.1.1', os.name: 'Linux', os.arch:
'amd64', os.version: '3.11.0-19-generic', java.version: '1.8.0'
Driver info: org.openqa.selenium.firefox.FirefoxDriver
Capabilities [{applicationCacheEnabled=true, rotatable=false, handlesAlerts=true, databaseEnabled=true,
version=28.0, platform=LINUX, browserConnectionEnabled=true, nativeEvents=false, acceptSslCerts=true,
webStorageEnabled=true, locationContextEnabled=true, browserName=firefox, takesScreenshot=true,
javascriptEnabled=true, cssSelectorsEnabled=true}]

Reported by sebastien.barbieri on 2014-04-17 14:20:45

lukeis commented 8 years ago

 ruby -v
ruby 2.1.1p76 (2014-02-24 revision 45161) [x86_64-linux]
cat weibo.rb 
require 'watir-webdriver'
browser = Watir::Browser.new(:firefox)#,{:profile => "default"})
browser.goto "weibo.com/"
browser.div(:class => "inp username").click
browser.text_field(:name => "username").set "13521499283"
##########
ruby weibo.rb
[remote server] file:///tmp/webdriver-profile20140422-28580-1apkp8w/extensions/fxdriver@googlecode.com/components/command_processor.js:8225:in
`fxdriver.preconditions.visible': Element is not currently visible and so may not be
interacted with (Selenium::WebDriver::Error::ElementNotVisibleError)
    from [remote server] file:///tmp/webdriver-profile20140422-28580-1apkp8w/extensions/fxdriver@googlecode.com/components/command_processor.js:10867:in
`DelayedCommand.prototype.checkPreconditions_'
    from [remote server] file:///tmp/webdriver-profile20140422-28580-1apkp8w/extensions/fxdriver@googlecode.com/components/command_processor.js:10884:in
`DelayedCommand.prototype.executeInternal_/h'
    from [remote server] file:///tmp/webdriver-profile20140422-28580-1apkp8w/extensions/fxdriver@googlecode.com/components/command_processor.js:10889:in
`DelayedCommand.prototype.executeInternal_'
    from [remote server] file:///tmp/webdriver-profile20140422-28580-1apkp8w/extensions/fxdriver@googlecode.com/components/command_processor.js:10831:in
`DelayedCommand.prototype.execute/<'
    from /home/baoyangc/.rvm/gems/ruby-2.1.1/gems/selenium-webdriver-2.41.0/lib/selenium/webdriver/remote/response.rb:51:in
`assert_ok'
    from /home/baoyangc/.rvm/gems/ruby-2.1.1/gems/selenium-webdriver-2.41.0/lib/selenium/webdriver/remote/response.rb:15:in
`initialize'
    from /home/baoyangc/.rvm/gems/ruby-2.1.1/gems/selenium-webdriver-2.41.0/lib/selenium/webdriver/remote/http/common.rb:59:in
`new'
    from /home/baoyangc/.rvm/gems/ruby-2.1.1/gems/selenium-webdriver-2.41.0/lib/selenium/webdriver/remote/http/common.rb:59:in
`create_response'
    from /home/baoyangc/.rvm/gems/ruby-2.1.1/gems/selenium-webdriver-2.41.0/lib/selenium/webdriver/remote/http/default.rb:66:in
`request'
    from /home/baoyangc/.rvm/gems/ruby-2.1.1/gems/selenium-webdriver-2.41.0/lib/selenium/webdriver/remote/http/common.rb:40:in
`call'
    from /home/baoyangc/.rvm/gems/ruby-2.1.1/gems/selenium-webdriver-2.41.0/lib/selenium/webdriver/remote/bridge.rb:634:in
`raw_execute'
    from /home/baoyangc/.rvm/gems/ruby-2.1.1/gems/selenium-webdriver-2.41.0/lib/selenium/webdriver/remote/bridge.rb:612:in
`execute'
    from /home/baoyangc/.rvm/gems/ruby-2.1.1/gems/selenium-webdriver-2.41.0/lib/selenium/webdriver/remote/bridge.rb:423:in
`clearElement'
    from /home/baoyangc/.rvm/gems/ruby-2.1.1/gems/selenium-webdriver-2.41.0/lib/selenium/webdriver/common/element.rb:141:in
`clear'
    from /home/baoyangc/.rvm/gems/ruby-2.1.1/gems/watir-webdriver-0.6.9/lib/watir-webdriver/user_editable.rb:14:in
`set'
    from weibo.rb:5:in `<main>'

Reported by BaoyangChai on 2014-04-22 15:23:00

lukeis commented 8 years ago

Please help me to understand why I am getting the below mention issue 

Element is not currently visible and so may not be interacted with (Selenium::WebDriver::Error::ElementNotVisibleError)

Selenium version: 2.32.1
OS: Windows 8
Browser: Firefox

Out of 5 , 2 times testcase getting executed sucessfully but 3 times I am getting the
above mentioned error so what change I should made to overcome this problem. Alos how
2 times it is executing sucessfuly?

Please look in to it.

Reported by garg.nikhil005 on 2014-05-01 06:18:21

lukeis commented 8 years ago

Ran into a similar problem with a text input element on a form. Element was visible,
and I could use the "Focus" keyword on it, but the "Input Text" keyword would fail
with the "not visible" error.

Found a workaround by providing a more explicit xpath to "Input Text".

Here the element that was giving the error:

<input id="description" type="text" maxlength="40" size="40" value="" name="description">

Here's the keyword call that was failing:

Input Text | description | dummyText

Here's the keyword call that succeeded:

Input Text | xpath=//input[@id='description'] | dummyText

Hope that helps.

Reported by wdomes on 2014-06-10 20:02:20

lukeis commented 8 years ago

i am also facing similar problem. mostly times it's automate fine no without issue.
But some time getting below issue----------
org.openqa.selenium.WebDriverException: [JavaScript Error: "e is null" {file: "file:///C:/Users/AppData/Local/Temp/anonymous8707730166287218402webdriver-profile/extensions/fxdriver@googlecode.com/components/command-processor.js"
line: 7854}]'[JavaScript Error: "e is null" {file: "file:///C:/Users/AppData/Local/Temp/anonymous8707730166287218402webdriver-profile/extensions/fxdriver@googlecode.com/components/command-processor.js"
line: 7854}]' when calling method: [nsICommandProcessor::execute]
Command duration or timeout: 52 milliseconds

Driver info: org.openqa.selenium.firefox.FirefoxDriver
Capabilities [{platform=WINDOWS, acceptSslCerts=true, javascriptEnabled=true, browserName=firefox,
rotatable=false, locationContextEnabled=true, version=33.0.3, cssSelectorsEnabled=true,
databaseEnabled=true, handlesAlerts=true, nativeEvents=false, webStorageEnabled=true,
applicationCacheEnabled=true, takesScreenshot=true}]
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
    at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:204)
    at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:156)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:599)
    at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:352)
    at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:449)
    at org.openqa.selenium.By$ByXPath.findElement(By.java:357)
    at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:344)
    at com.domino.selenium.pages.charts.ScenarioEvaluatorCharts.evaluatorSummary(ScenarioEvaluatorCharts.java:40)
    at com.domino.selenium.pages.ScenarioEvaluatorChartPage.scenarioEvaluatorChartExecution(ScenarioEvaluatorChartPage.java:24)
    at com.domino.selenium.test.suite.MultiUserTestSuite.scenarioEvaluatorChartExecution(MultiUserTestSuite.java:122)
    at com.domino.selenium.test.suite.MultiUserTestSuite.run(MultiUserTestSuite.java:65)
    at java.lang.Thread.run(Thread.java:662)

Reported by rah8singh on 2014-11-07 14:22:57

lukeis commented 8 years ago

another problem similar as - org.openqa.selenium.ElementNotVisibleException: Element
is not currently visible and so may not be interacted with
Command duration or timeout: 19 milliseconds

thanks in advance

Reported by rah8singh on 2014-11-07 14:24:46

lukeis commented 8 years ago

Hi,

I am also facing same issue :

Version : 2.43.1
Windows : XP
Firefox

Exception in thread "main" org.openqa.selenium.ElementNotVisibleException: Element
is not currently visible and so may not be interacted with
Command duration or timeout: 28 milliseconds
Build info: version: '2.43.1', revision: '5163bce', time: '2014-09-10 16:27:58'
System info: host: 'home-PC', ip: '192.168.1.5', os.name: 'Windows 7', os.arch: 'x86',
os.version: '6.1', java.version: '1.7.0_71'
Session ID: a3789485-3e48-46e4-92bf-415cdaf73953
Driver info: org.openqa.selenium.firefox.FirefoxDriver
Capabilities [{platform=WINDOWS, databaseEnabled=true, cssSelectorsEnabled=true, javascriptEnabled=true,
acceptSslCerts=true, handlesAlerts=true, browserName=firefox, webStorageEnabled=true,
nativeEvents=false, rotatable=false, locationContextEnabled=true, applicationCacheEnabled=true,
takesScreenshot=true, version=33.1.1}]
    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:204)
    at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:156)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:599)
    at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:268)
    at org.openqa.selenium.remote.RemoteWebElement.click(RemoteWebElement.java:79)
    at SeleniumWeb.main(SeleniumWeb.java:28)
Caused by: org.openqa.selenium.ElementNotVisibleException: Element is not currently
visible and so may not be interacted with
Build info: version: '2.43.1', revision: '5163bce', time: '2014-09-10 16:27:58'
System info: host: 'home-PC', ip: '192.168.1.5', os.name: 'Windows 7', os.arch: 'x86',
os.version: '6.1', java.version: '1.7.0_71'
Driver info: driver.version: unknown
    at <anonymous class>.fxdriver.preconditions.visible(file:///C:/Users/home/AppData/Local/Temp/anonymous859489714626108694webdriver-profile/extensions/fxdriver@googlecode.com/components/command-processor.js:8936:12)
    at <anonymous class>.DelayedCommand.prototype.checkPreconditions_(file:///C:/Users/home/AppData/Local/Temp/anonymous859489714626108694webdriver-profile/extensions/fxdriver@googlecode.com/components/command-processor.js:11595:15)
    at <anonymous class>.DelayedCommand.prototype.executeInternal_/h(file:///C:/Users/home/AppData/Local/Temp/anonymous859489714626108694webdriver-profile/extensions/fxdriver@googlecode.com/components/command-processor.js:11612:11)
    at <anonymous class>.DelayedCommand.prototype.executeInternal_(file:///C:/Users/home/AppData/Local/Temp/anonymous859489714626108694webdriver-profile/extensions/fxdriver@googlecode.com/components/command-processor.js:11617:7)
    at <anonymous class>.DelayedCommand.prototype.execute/<(file:///C:/Users/home/AppData/Local/Temp/anonymous859489714626108694webdriver-profile/extensions/fxdriver@googlecode.com/components/command-processor.js:11559:5)

Reported by kishore.thotapally on 2014-12-04 01:37:05

lukeis commented 8 years ago

Is there any solution to this issue yet.. Im currently facing the same problem.. Eventhough
the control is present and I can see that its is enabled, webdriver returns the : ->
error: Element is not currently visible and so may not be interacted with
Any help would be greatly appreciated.

Reported by joebadmus on 2015-01-05 13:47:26

lukeis commented 8 years ago

Hi, I am also facing same issue but in chrome browser

Selenium Version:-2.44
Browser:-Chrome
OS:- Windows 8.1

My script is working fine in Firefox browser but while executing in Chrome it is throwing
following issue (Element not visible)
Is there any issue with chrome browser version? please let me know.

org.openqa.selenium.ElementNotVisibleException: element not visible
  (Session info: chrome=43.0.2357.124)
  (Driver info: chromedriver=2.13.307647 (5a7d0541ebc58e69994a6fb2ed930f45261f3c29),platform=Windows
NT 6.3 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 26 milliseconds
Build info: version: '2.44.0', revision: '76d78cf', time: '2014-10-23 20:02:37'
System info: host: 'DGL-10010', ip: '192.168.10.149', os.name: 'Windows 8', os.arch:
'amd64', os.version: '6.2', java.version: '1.7.0_25'
Session ID: 689bf7c7ba14370be1b957b4b7776a1b
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{platform=WIN8, acceptSslCerts=true, javascriptEnabled=true, browserName=chrome,
chrome={userDataDir=C:\Users\Sangita\AppData\Local\Temp\scoped_dir6476_16089}, rotatable=false,
locationContextEnabled=true, mobileEmulationEnabled=false, version=43.0.2357.124, takesHeapSnapshot=true,
cssSelectorsEnabled=true, databaseEnabled=false, handlesAlerts=true, browserConnectionEnabled=false,
webStorageEnabled=true, nativeEvents=true, applicationCacheEnabled=false, 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:526)
    at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:204)
    at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:156)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:599)
    at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:268)
    at org.openqa.selenium.remote.RemoteWebElement.click(RemoteWebElement.java:79)
    at org.digigrapes.qa.jeevom.Base.BaseClass.clickElement(BaseClass.java:127)
    at org.digigrapes.qa.jeevom.userProfile.LoginFn.Login(LoginFn.java:40)
    at org.digigrapes.qa.jeevom.userProfile.LoginFn.LoginToApp(LoginFn.java:25)
    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:606)
    at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
    at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
    at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
    at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
    at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
    at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
    at org.testng.TestRunner.privateRun(TestRunner.java:767)
    at org.testng.TestRunner.run(TestRunner.java:617)
    at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
    at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
    at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
    at org.testng.SuiteRunner.run(SuiteRunner.java:240)
    at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
    at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
    at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224)
    at org.testng.TestNG.runSuitesLocally(TestNG.java:1149)
    at org.testng.TestNG.run(TestNG.java:1057)
    at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:111)
    at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:204)
    at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:175)

Reported by saurabh.san17 on 2015-07-06 11:19:34

lukeis commented 8 years ago

Finally this worked for me. Element is not currently visible and so may not be interacted
with.

Initially it was like test was successful only 2 of 5 times. Was not sure how it was
working sometimes and others not.

Solution:

[Worked by reducing the security settings in IE. Enable all activeX controls. Enable
scripts and IFRAMES also. Some of these will warn to put computer at risk, but it was
the only solution I had. Introduce Explicit wait by using presenceOfElementLocated
instead of visibilityOfElementLocated at every point where page load takes time.]

Reported by akshay.upadhayay on 2015-08-13 03:38:33

lukeis commented 8 years ago

i am also facing the same issue

Reported by satheeshg15 on 2015-08-25 10:25:12

lukeis commented 8 years ago

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

Labels added: Restrict-AddIssueComment-Commit