"Element cannot be scrolled into view" error with 2.15.0

12,273 views
Skip to first unread message

Vincent Massol

unread,
Dec 8, 2011, 3:30:49 PM12/8/11
to webd...@googlegroups.com
Hi guys,

Just installed 2.15.0 and I now get "Element cannot be scrolled into view" on a test that was passing before. Any idea what I should look for?

Precise error:


Thanks
-Vincent

Vincent Massol

unread,
Dec 8, 2011, 3:34:08 PM12/8/11
to webd...@googlegroups.com
Here's a portion of the test:

        final By objectLocator = By.id("xobject_" + className + "_" + index);
        final WebElement objectContainer = getDriver().findElement(objectLocator);
        WebElement deleteLink = objectContainer.findElement(By.className("delete"));
        deleteLink.click();

Apparently it's the click() that generates the error now.

Daniel Wagner-Hall

unread,
Dec 8, 2011, 6:17:40 PM12/8/11
to webd...@googlegroups.com
We would absolutely love the full HTML, Javascript and CSS for a page
which shows this problem.

Ideally, reduced to the simplest case you can (i.e. the least HTML)

> --
> You received this message because you are subscribed to the Google Groups
> "webdriver" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/webdriver/-/Kurz0g8tIwoJ.
>
> To post to this group, send email to webd...@googlegroups.com.
> To unsubscribe from this group, send email to
> webdriver+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/webdriver?hl=en.

Ryan Bigg

unread,
Dec 8, 2011, 9:00:06 PM12/8/11
to webdriver
We're also getting this error on our build:

http://travis-ci.org/#!/spree/spree/builds/387795/L185

Error seems to have only appeared when this version was bumped.

Simon Stewart

unread,
Dec 9, 2011, 8:15:35 AM12/9/11
to webd...@googlegroups.com
If you can provide a reduced test case demonstrating this problem, we'd be far more likely to fix this problem: at the moment none of the dev team are seeing this issue.

Paul recently suggested setting up a regression tests project for this sort of thing. This seems like the perfect candidate for trying this process out. Could you consider heading over to the site and following the instructions there?


The instructions say to use groovy. If you're not comfortable with that, python or any other language supported by the core selenium project would be fine.

Many thanks,

Simon

--
You received this message because you are subscribed to the Google Groups "webdriver" group.

dkellis

unread,
Dec 9, 2011, 6:44:33 PM12/9/11
to webdriver
All,
I just revved to 2.15 and am seeing the "element cannot be scrolled
into view" also, in previously-working test code.

Our pages are generated by a server using Java and GWT--can you
suggest how to submit a reproduction page in this case?

Thanks,

Dave

PS: Mac Lion and FF 6.0.2.

Keith Pitt

unread,
Dec 12, 2011, 1:22:52 AM12/12/11
to webdriver
Hey guys,

So I think I've tracked down the source of this issue. I don't have
any tests cases to upload because I'm short on time, but perhaps
someone else can give it a crack.

I was getting this error locally, and I figured it was a problem with
my app, not selenium. So after digging around, I believe I had some
dodgy CSS. Take this example:

<a href="/foo/bar" class="delete"><span class="icon"></span></a>

.delete .icon {
float: left;
width: 50px;
height: 50px;
background: red;
}

Here we have a anchor that has a red block inside it. This element can
be interacted with by the user *but* from the browsers perspective,
its got no layout. Checking in firebug reports it has having no
bounding box. Because the span is floating within the a, its not
giving any bounds to the anchor.

After changing it to:

a.delete {
float: left;
overflow: hidden;
display: block;
}

My test worked. I believe this is the issue. Selenium can't scroll to
it because it has no bounds. I could be talking bollocks here, but
this changed worked for me. Perhaps it can point someone in the right
direction.

Keith

oreny

unread,
Dec 14, 2011, 5:32:22 AM12/14/11
to webdriver
Maybe this will shed some light:
We get this error when testing some page using WebDriver and Xvfb
running in 768x1024.
When we test it in regular X server - the problem doesn't show
if we run Xvfb in 1024x4096 - the problem goes away.

iamcpizzle

unread,
Dec 14, 2011, 5:25:18 PM12/14/11
to webdriver
I'm also getting this error and it happens when I purposely keep my FF
windows a bit small (to mimic mobile device screen size) and some
elements on the page aren't fully visible right on the screen. Perhaps
it's not resizing all buttons quickly enough. What's interesting is
when I do a screenshot of the page, all elements are visible. I don't
have control over the app that I'm testing so i can't change the css
(if that is the culprit mentioned above). Will be reverting back to
2.14 for now.

bemcho

unread,
Dec 16, 2011, 3:37:16 AM12/16/11
to webdriver
Yep same on my side
happens on click
selenium 2.15/ FirefoxDriver / FF 9 beta 4

[java] [2011-12-16 10:29:07.042]
org.openqa.selenium.interactions.MoveTargetOutOfBoundsException:
Element cannot be scrolled into view:[object HTMLInputElement]
[java] Command duration or timeout: 101 milliseconds
[java] Build info: version: '2.15.0', revision: '15105', time:
'2011-12-08 09:57:28'
[java] System info: os.name: 'Windows 7', os.arch: 'amd64',
os.version: '6.1', java.version: '1.7.0_01'
[java] Driver info: driver.version: RemoteWebDriver
[java] at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
[java] at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:
57)
[java] at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:
45)
[java] at
java.lang.reflect.Constructor.newInstance(Constructor.java:525)
[java] at
org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:
147)
[java] at
org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:
113)
[java] at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:
424)
[java] at
org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:
231)
[java] at
org.openqa.selenium.remote.RemoteWebElement.click(RemoteWebElement.java:
72)
[java] at sun.reflect.GeneratedMethodAccessor28.invoke(Unknown
Source)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
43)
[java] at java.lang.reflect.Method.invoke(Method.java:601)
[java] at org.openqa.selenium.support.events.EventFiringWebDriver
$EventFiringWebElement$1.invoke(EventFiringWebDriver.java:325)
[java] at $Proxy2.click(Unknown Source)
[java] at org.openqa.selenium.support.events.EventFiringWebDriver
$EventFiringWebElement.click(EventFiringWebDriver.java:338)
[java] at
com.intershop.tools.etest.web.seleniumdriver.WebSubmitButtonImpl.submit(WebSubmitButtonImpl.java:
25)
[java] at
com.intershop.tools.etest.web.selenium.TestAgainstSeleniumWebDriverStrategyImpl.submitWithName(TestAgainstSeleniumWebDriverStrategyImpl.java:
2658)
[java] at
com.intershop.tools.etest.web.HTTPTestCase.submitWithName(HTTPTestCase.java:
2137)
[java] at
com.intershop.tools.etest.web.WebTester.submitWithName(WebTester.java:
893)
[java] at
tests.features.com.intershop.sellside.mother.channel.ChannelPromotionMother.createPromotionInPromotionList(ChannelPromotionMother.java:
297)
[java] at
tests.features.com.intershop.sellside.mother.channel.ChannelPromotionMother.createPromotionInPromotionList(ChannelPromotionMother.java:
258)
[java] at
tests.features.com.intershop.sellside.mother.channel.ChannelPromotionMother.createPromotionInPromotionList(ChannelPromotionMother.java:
211)
[java] at
tests.features.com.intershop.sellside.mother.channel.ChannelPromotionMother.createPromotion(ChannelPromotionMother.java:
198)
[java] at
tests.features.com.intershop.sellside.mother.channel.ChannelPromotionMother.createPromotionInPromotionList(ChannelPromotionMother.java:
184)
[java] at
tests.features.com.intershop.sellside.mother.channel.ChannelPromotionMother.createPromotion(ChannelPromotionMother.java:
173)
[java] at
tests.smoke.com.intershop.sellside.channel.consumer.promotion.PromotionTest.setUp(PromotionTest.java:
36)
[java] at
tests.features.com.intershop.ucm.util.UCMHTTPTestCase.runBare(UCMHTTPTestCase.java:
217)
[java] at junit.framework.TestResult$1.protect(TestResult.java:
110)
[java] at junit.framework.TestResult.runProtected(TestResult.java:
128)
[java] at junit.framework.TestResult.run(TestResult.java:113)
[java] at junit.framework.TestCase.run(TestCase.java:124)
[java] at
tests.features.com.intershop.ucm.util.UCMHTTPTestCase.run(UCMHTTPTestCase.java:
279)
[java] at junit.framework.TestSuite.runTest(TestSuite.java:243)
[java] at junit.framework.TestSuite.run(TestSuite.java:238)
[java] at com.intershop.tools.etest.client.ISTestRunnerFrame
$15.run(ISTestRunnerFrame.java:571)
[java]
[java] [2011-12-16 10:29:07.042]

jaiew

unread,
Dec 15, 2011, 10:58:25 PM12/15/11
to webdriver
Yep Keith has pinpointed a test case that reproduces the failure.

html:

<!DOCTYPE html>
<html>
<head>
<style type="text/css">
.delete {

}
.delete .icon {
float: left;
width: 50px;
height: 50px;
background: red;
}

</style>
</head>
<body>
<a href="#" class="delete"><span class="icon"></span></a>
</body>

</html>

java test case:
@Test
public void testIssue() {
driver..get("http://localhost:5990/html/bounding-issue.html");
driver.findElement(By.className("delete")).click();
}


Stack trace:
org.openqa.selenium.remote.RemoteWebDriver execute
INFO: Executing: [null, newSession
{"desiredCapabilities":"Capabilities [{platform=ANY,
browserName=firefox, version=}]"}]
org.openqa.selenium.remote.RemoteWebDriver execute
INFO: Executing: [d42c63a7-a3c1-7842-a991-aef4da6bc5dd, get
{"url":"http://localhost:5990/html/bounding-issue.html"}]
org.openqa.selenium.remote.RemoteWebDriver execute
INFO: Executing: [d42c63a7-a3c1-7842-a991-aef4da6bc5dd, findElement
{"using":"class name","value":"delete"}]
org.openqa.selenium.remote.RemoteWebDriver execute
INFO: Executing: [d42c63a7-a3c1-7842-a991-aef4da6bc5dd, clickElement
{"id":"{2423bf83-dd7e-2c4f-9385-cb4ad78e8db7}"}]
6811 [main] ERROR
com.atlassian.webdriver.testing.rule.WebDriverScreenshotRule -
Element cannot be scrolled into view:http://localhost:5990/html/
bounding-issue.html#
Command duration or timeout: 32 milliseconds


Build info: version: '2.15.0', revision: '15105', time: '2011-12-08

12:59:39'
System info: os.name: 'Mac OS X', os.arch: 'x86_64', os.version:
'10.6.6', java.version: '1.6.0_22'
Driver info: driver.version: RemoteWebDriver
org.openqa.selenium.interactions.MoveTargetOutOfBoundsException:
Element cannot be scrolled into view:http://localhost:5990/html/
bounding-issue.html#
Command duration or timeout: 32 milliseconds


Build info: version: '2.15.0', revision: '15105', time: '2011-12-08

12:59:39'
System info: os.name: 'Mac OS X', os.arch: 'x86_64', os.version:
'10.6.6', java.version: '1.6.0_22'
Driver info: driver.version: RemoteWebDriver
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:
147)
at
org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:
113)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:
424)
at
org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:
231)
at
org.openqa.selenium.remote.RemoteWebElement.click(RemoteWebElement.java:
72)


Cheers,
Jaie

Srikanth G

unread,
Dec 21, 2011, 3:42:55 AM12/21/11
to webd...@googlegroups.com
Hi All,

Apologies for my ignorance, so is there any workaround for this problem? or Should I be waiting for the fix tobe released?
--
-Thanks
-Srikanth.G
-Google India Ltd
-Hyderabad

Jeff Bowman

unread,
Jan 3, 2012, 12:41:42 PM1/3/12
to webd...@googlegroups.com
This happens for every page that doesn't completely fit on the screen and for which the script tries to click a radio button (in my case). It does seem to scroll to text fields, just not radio buttons (possibly other controls). Additionally adding:

((FirefoxDriver)driver).getKeyboard().pressKey(Keys.PAGE_DOWN); 

does not help. The page down works as expected, and, in my case the radio buttons are now visible on the screen, however I continue to get:

ERROR: Element cannot be scrolled into view: [object HTMLInputElement]...

Jeff

Pavithra

unread,
Jan 9, 2012, 6:29:00 AM1/9/12
to webdriver, simon.m...@gmail.com
Hi,
I am using selenium 2.13.0 and I am facing the same issue on Mac
Firefox browsers and not on windows.

Is there any workaround or solution yet ?

Thanks,
Pavithra

Emil Tomov

unread,
Jan 9, 2012, 6:46:24 AM1/9/12
to webd...@googlegroups.com
Same with 2.16 FF 10


--
You received this message because you are subscribed to the Google Groups "webdriver" group.

shen xieyin

unread,
Jan 10, 2012, 10:15:20 PM1/10/12
to webd...@googlegroups.com
we met the same issue in 2.16, could anyone take a look?

2012/1/9 Emil Tomov <bem...@gmail.com>

Kfir Harel

unread,
Jan 15, 2012, 6:17:45 AM1/15/12
to webd...@googlegroups.com
Hi,

I'm facing the same issue using FF and 2.15.0
Is there any fix??

Daniel Wagner-Hall

unread,
Jan 16, 2012, 11:09:49 AM1/16/12
to webd...@googlegroups.com
We're working on it - there are actually a number of problems in play
here. Unfortunately this hasn't been fixed in 2.17, but will
hopefully be in 2.18 which should be out soon. Track this issue for
progress: https://code.google.com/p/selenium/issues/detail?id=3075

Srikanth G

unread,
Jan 17, 2012, 6:04:05 AM1/17/12
to webd...@googlegroups.com
Thanks for the Update!

Simon Stewart

unread,
Jul 3, 2012, 4:24:43 PM7/3/12
to webd...@googlegroups.com
We thought we'd caught all the issues. If there's still a case we've
missed, please create a reproducible test case and add it to the
existing one. It's only with these reproducible test cases that we've
got a fighting chance of fixing things.

Simon

On Tue, Jul 3, 2012 at 4:23 PM, goonerfromlag <gunner...@gmail.com> wrote:
> Hello, has there been any progress with this issue? I'm getting it with 2.19
> and FF versions 3.6, 7.0, 9.0, 10.0.2. Switching to FF 10.0.2 solved this
> for me on windows, but I'm stuck in Ubuntu-10.04.4.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/webdriver/-/946vp0gr5JcJ.

Sirisha

unread,
Jul 14, 2012, 2:31:37 PM7/14/12
to webd...@googlegroups.com
Hi,

Please find the test cases steps to reproduce the issue.

package tests;

import java.util.concurrent.TimeUnit;

import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import org.openqa.selenium.firefox.FirefoxDriver;
import org.openqa.selenium.firefox.FirefoxProfile;
import org.openqa.selenium.ie.InternetExplorerDriver;
import org.openqa.selenium.interactions.Actions;
import org.testng.annotations.Test;

public class MouseOver {
   
    @Test
    public void mouseOver()
    {
        FirefoxProfile p = new FirefoxProfile();
        p.setEnableNativeEvents(false);
        WebDriver driver = new FirefoxDriver(p);

        driver.get("http://spicejet.com");
        driver.manage().timeouts().implicitlyWait(30000, TimeUnit.MILLISECONDS);
        Actions actions = new Actions(driver);
        WebElement we = driver.findElement(By.linkText("about us"));
        actions.moveToElement(we);
        actions.click().perform();
        actions.moveToElement(driver.findElement(By.linkText("investors")));
        actions.click().perform();

        actions.moveToElement(driver.findElement(By.linkText("annual reports")));
        actions.click().perform();
        actions.moveToElement(driver.findElement(By.linkText("annual report 2008-09")));
        actions.click().perform();
     driver.findElement(By.linkText("annual report 2008-09")).click();
           
       
    }

}


FAILED: mouseOver
org.openqa.selenium.interactions.MoveTargetOutOfBoundsException: Element cannot be scrolled into view:http://spicejet.com/# (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 16 milliseconds
Build info: version: '2.24.1', revision: '17205', time: '2012-06-19 17:28:14'
System info: os.name: 'Windows XP', os.arch: 'x86', os.version: '5.1', java.version: '1.6.0_33'
Driver info: driver.version: RemoteWebDriver
Session ID: 55ae2c97-78e6-4c4e-be4f-bd948b8c744e
    at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:188)
    at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:145)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:472)
    at org.openqa.selenium.remote.RemoteExecuteMethod.execute(RemoteExecuteMethod.java:34)
    at org.openqa.selenium.remote.RemoteMouse.mouseMove(RemoteMouse.java:88)
    at org.openqa.selenium.interactions.MoveMouseAction.perform(MoveMouseAction.java:36)
    at org.openqa.selenium.interactions.CompositeAction.perform(CompositeAction.java:31)
    at org.openqa.selenium.interactions.Actions.perform(Actions.java:348)
    at tests.MouseOver.mouseOver(MouseOver.java:35)
... Removed 26 stack frames
>>> >>>> webdriver+unsubscribe@googlegroups.com.
>>> >>>> For more options, visit this group at
>>> >>>> http://groups.google.com/group/webdriver?hl=en.
>>> >>>>
>>> >>>
>>> >>> --
>>> >>> You received this message because you are subscribed to the Google
>>> >>> Groups
>>> >>> "webdriver" group.
>>> >>> To post to this group, send email to webd...@googlegroups.com.
>>> >>> To unsubscribe from this group, send email to
>>> >>> webdriver+unsubscribe@googlegroups.com.
>>> >>> For more options, visit this group at
>>> >>> http://groups.google.com/group/webdriver?hl=en.
>>> >>
>>> >>
>>> >> --
>>> >> You received this message because you are subscribed to the Google
>>> >> Groups
>>> >> "webdriver" group.
>>> >> To post to this group, send email to webd...@googlegroups.com.
>>> >> To unsubscribe from this group, send email to
>>> >> webdriver+unsubscribe@googlegroups.com.
>>> >> For more options, visit this group at
>>> >> http://groups.google.com/group/webdriver?hl=en.
>>> >
>>> >
>>> > --
>>> > You received this message because you are subscribed to the Google
>>> > Groups
>>> > "webdriver" group.
>>> > To post to this group, send email to webd...@googlegroups.com.
>>> > To unsubscribe from this group, send email to
>>> > webdriver+unsubscribe@googlegroups.com.
>>> > For more options, visit this group at
>>> > http://groups.google.com/group/webdriver?hl=en.
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "webdriver" group.
>>> To post to this group, send email to webd...@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> webdriver+unsubscribe@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/webdriver?hl=en.
>>>
>>
>>
>>
>> --
>> -Thanks
>> -Srikanth.G
>> -Google India Ltd
>> -Hyderabad
>
> --
> You received this message because you are subscribed to the Google Groups
> "webdriver" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/webdriver/-/946vp0gr5JcJ.
>
> To post to this group, send email to webd...@googlegroups.com.
> To unsubscribe from this group, send email to
> webdriver+unsubscribe@googlegroups.com.

Sirisha

unread,
Jul 14, 2012, 2:32:12 PM7/14/12
to webd...@googlegroups.com
Version : 2.24.1, FF 90

Simon Stewart

unread,
Mar 6, 2013, 3:37:41 PM3/6/13
to webd...@googlegroups.com
qq: could a user scroll the centre of that element into the viewport of the running browser?

Simon

On Tue, Mar 5, 2013 at 7:05 AM, Ankush Sawant <go2s...@gmail.com> wrote:
Hi friends,

I installed build 2.25.0 then 2.28.0 then 2.31.0 with different versions of firefox but I'm still facing the same issue
org.openqa.selenium.interactions.MoveTargetOutOfBoundsException: Element cannot be scrolled into view:[object HTMLInputElement]
Element cannot be scrolled into view:[object HTMLInputElement]
Any one with any work around for this?

Ankush
--
You received this message because you are subscribed to the Google Groups "webdriver" group.
To unsubscribe from this group and stop receiving emails from it, send an email to webdriver+...@googlegroups.com.

To post to this group, send email to webd...@googlegroups.com.

ash

unread,
Mar 6, 2013, 3:40:26 PM3/6/13
to webd...@googlegroups.com
@Rohit: It's the same hover problem that i faced a while ago. The code only works with FF10 so i've downgraded to FF10.
 
@Simon: I have similiar hover menu problem that only works in FF10. It doesn't work on newer versions although it works on chrome.
 
Can this issue be escalated to be fixed first? It's already been 10 releases past FF10 and this issue still exists.
 
Thanks

Simon Stewart

unread,
Mar 6, 2013, 5:10:42 PM3/6/13
to webd...@googlegroups.com
We're an Open Source project, and although we have contributors from plenty of well known companies, we don't have an escalation policy and instituting one isn't practical. Think of it as more like herding cats than a command and control structure. Given that, the best way to get a bug fixed is to make it as simple as possible for someone to reproduce your issue on their own machine. Here's what would be really helpful:

* What OS are you on? Which version of that OS? "Windows 7" or "Ubuntu Hardy" for example.

* Which browser are you using? And which version? "Firefox 17" or "IE 9" for example.

* Can you supply a reduced test case? A single HTML page and a webdriver test that demonstrates the problem is what we're looking for. Yes, I know your app is super secret and you could never provide us with an actual page from it. Feel free to anonymize content, or rework the HTML or whatever. All we need is that reproducible test case.

* The link to the bug you create with all that information in.

Being honest, the core team is relatively small and very busy, so even with all that we may not be able to get to it. It's not because we think fixing bugs is not important, it's because there just aren't enough hours in the day. Being more honest, a bug that's lacking the above information is something that I would normally just skim past because there's nothing "actionable" about it. At least with it, you've a chance of having your issue addressed. (Aside: I also look at "star" counts on Google Code)

I know that's not quite what you wanted to hear. You also probably don't want to hear how we're really happy to help people get up to speed on our code base, or how we now use git as our source control system specifically to make it easier for people to send us patches. You may not be interested that we reworded our CLA to make it so easy to understand and so lightweight that even the most skittish of lawyers won't freak out when reading it. Those may be things you're not interested in hearing, but all these things are true, and I'd really appreciate the help.

Cheers,

Simon

ash

unread,
Mar 6, 2013, 5:31:45 PM3/6/13
to webd...@googlegroups.com
Thank you simon for the response.
 
Here's the bug http://code.google.com/p/selenium/issues/detail?id=3075 that has already been logged for this issue although this bug is particularly for watir. Nevertheless, it's happening in Java/Webdriver in Firefox.
 
My work application has hover menu all over the page so in order to have my automation code working, i had no other option than to downgrade FF to 10.0
 
Due to this issue, i can't run my code in jenkins server other than local jenkins since the linux server FF cannot be configured by me.

Bill Ross

unread,
Mar 6, 2013, 6:26:06 PM3/6/13
to webd...@googlegroups.com
It might be interesting to query the coords of the element. I had this
symptom with an element that was positioned way off the screen in negative
space to make it invisible.

Bill

Marcus Merrell

unread,
Mar 6, 2013, 8:59:26 PM3/6/13
to webd...@googlegroups.com, webd...@googlegroups.com
I'd like to note here that Selenium Conference 2013 will feature a half-day workshop, run by Simon, which will go over the Selenium internals, build system, configuration, and other vitals that you need in order to fix a bug or even become a committer. It should be pretty amazing, as it was last year. 

I'd like to see a full house for that, but also to invite anyone reading this thread to get more involved in helping the core committers. Selenium/WebDriver feeds my family and tens of thousands more, and it seems unreasonable for a couple dozen volunteers to have to do it all alone. Now that this project has made me a stronger developer, I plan to start giving back as much as I can. 

MM

Sent from my iPhone

ash

unread,
Mar 7, 2013, 2:38:34 PM3/7/13
to webd...@googlegroups.com
Trying to revamp this thread, the bug that has been logged for this issue http://code.google.com/p/selenium/issues/detail?id=3075  has been there for more than a two years now.

Is there any plan to have this issue fixed? 

Without this issue fixed, i am being handicapped here since it only works on FF10 and i can't configure FF in jenkins server used for all the projects at my work.

Thanks

Simon Stewart

unread,
Mar 12, 2013, 7:33:03 AM3/12/13
to webd...@googlegroups.com
I refer the honorable gentleman to my previous answer. The bug report with repros is an incredibly useful thing to have and helps an awful lot, but, as you can see, we've not got a lot of spare capacity to actually get this fixed: it's not something that appears to have wide impact on our users (though it's obviously very irksome when it happens to you). We'd really appreciate your help getting a fix in place :)

If you'd like to get started with the codebase, just let us know. The best place to get help getting up to speed is the #selenium IRC channel, but I'd be more than happy to revamp the docs in the wiki if there are holes.

Simon

Bill Ross

unread,
Apr 19, 2013, 7:14:29 PM4/19/13
to webd...@googlegroups.com
If you get the coordinates, maybe this will explain. E.g. the element
may be placed in negative-signed coordinate space to make it invisible.

Bill

Ashwini Chitale <amchi...@gmail.com> wrote:

> Hello friends,
>
> I am new to Selenium and using version 2.32. I get following error, can you
> please help?
>
> org.openqa.selenium.
> interactions.MoveTargetOutOfBoundsException:
> Element cannot be scrolled into
> view:
> http://globalunlockedphone.com/xchange/XChangeTest/website/user/register
> Command duration or timeout: 47 milliseconds
> Build info: version: '2.31.0', revision: '1bd294d', time: '2013-02-27
> 20:53:56'
> System info: os.name: 'Windows 7', os.arch: 'amd64', os.version:
> '6.1', java.version: '1.7.0_04'
> Session ID: b9a8a4b7-2e57-4f77-ae19-2461b6ecfbe3
> Driver info: org.openqa.selenium.firefox.FirefoxDriver
> Capabilities [{platform=XP, acceptSslCerts=true,
> javascriptEnabled=true, browserName=firefox, rotatable=false,
> locationContextEnabled=true, version=20.0.1, cssSelectorsEnabled=true,
> databaseEnabled=true, handlesAlerts=true,
> browserConnectionEnabled=true, nativeEvents=true,
> webStorageEnabled=true, applicationCacheEnabled=true,
> takesScreenshot=true}]
> 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:187)
> 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.RemoteWebElement.exe
>
>
>
> On Thursday, 8 December 2011 15:17:40 UTC-8, Daniel Wagner-Hall wrote:
> >
> > We would absolutely love the full HTML, Javascript and CSS for a page
> > which shows this problem.
> >
> > Ideally, reduced to the simplest case you can (i.e. the least HTML)
> >
> > On 8 December 2011 20:34, Vincent Massol <vma...@gmail.com <javascript:>>
> > wrote:
> > > Here's a portion of the test:
> > >
> > > final By objectLocator = By.id("xobject_" + className + "_" +
> > > index);
> > > final WebElement objectContainer =
> > > getDriver().findElement(objectLocator);
> > > WebElement deleteLink =
> > > objectContainer.findElement(By.className("delete"));
> > > deleteLink.click();
> > >
> > > Apparently it's the click() that generates the error now.
> > >
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > > "webdriver" group.
> > > To view this discussion on the web visit
> > > https://groups.google.com/d/msg/webdriver/-/Kurz0g8tIwoJ.
> > >
> > > To post to this group, send email to webd...@googlegroups.com<javascript:>
> > .
> > > To unsubscribe from this group, send email to
> > > webdriver+...@googlegroups.com <javascript:>.
> > > For more options, visit this group at

ash

unread,
Apr 19, 2013, 7:35:05 PM4/19/13
to webd...@googlegroups.com
What browser are you using for the test?

If it is Firefox, try installing FF10 and run 


On 8 December 2011 20:34, Vincent Massol <vma...@gmail.com> wrote:
> Here's a portion of the test:
>
>         final By objectLocator = By.id("xobject_" + className + "_" +
> index);
>         final WebElement objectContainer =
> getDriver().findElement(objectLocator);
>         WebElement deleteLink =
> objectContainer.findElement(By.className("delete"));
>         deleteLink.click();
>
> Apparently it's the click() that generates the error now.
>
> --
> You received this message because you are subscribed to the Google Groups
> "webdriver" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/webdriver/-/Kurz0g8tIwoJ.
>

> To post to this group, send email to webd...@googlegroups.com.


> To unsubscribe from this group, send email to


> For more options, visit this group at
> http://groups.google.com/group/webdriver?hl=en.

Bianca

unread,
Jul 29, 2013, 4:54:52 AM7/29/13
to webd...@googlegroups.com
Hello,

Here's just one of the posts out there that contains a HTML example http://stackoverflow.com/questions/16087961/selenium-element-cannot-be-scrolled-into-view-34-using-nunit-c-sharp 

It would be really good if this issue was fixed. It's been years now and users are still getting it. It's not a matter of a certain Selenium/browser anymore, it's happening on all the versions from the last 1-2 years, at least.

In my case I'm getting the error whenever I want to click a button in a confirmation wizard that is being displayed using an animation (jQuery.reveal with different animations, like 'fadeAndPop', see example from http://zurb.com/playground/reveal-modal-plugin). And in the application I'm testing, there are a lot of these confirmation wizards, so I have many tests failing randomly with this error.

I've tried using multiple ways waiting for the button's element, before interacting with it (Visible/Clickable/Present)
  • wait.until(ExpectedConditions.visibilityOf(_element_)).click();
  • wait.until(ExpectedConditions.visibilityOfElementLocated(By.id("element_id"))).click();
  • wait.until(ExpectedConditions.elementToBeClickable(By.id("element_id"))).click();
It's really frustrating that despite of using the proper methods to wait for the needed HTML element, they are of no use, in this case. The call to <wait + click> on the element generates the "element cannot be scrolled into view ..." immediately, without waiting at all. The wizard is displayed in less than 1 sec, so I'm in the situation where I visualy see the wizard being displayed, just as the <wait+click> command fails. In other cases (a new page is loaded, an hidden section is being displayed, etc) the above wait methods work fine.

Hopefully someone will look into this issue again and be able to solve it :)

Mike Riley

unread,
Aug 1, 2013, 1:05:33 PM8/1/13
to webd...@googlegroups.com
Just mentioning it in a forum does not get a problem looked at.

You need to file an issue, preferably with a reproducible test case, which it sounds like you have here.

Mike
Message has been deleted

Ankush Sawant

unread,
Aug 27, 2013, 4:21:11 AM8/27/13
to webd...@googlegroups.com

Hi All,

Few months back when I faced this issue, I posted on this group and carried out 
my task with some workaround (used Sikuli). I thought that with some latest 
releases this issue will be resolved.
But again I tested it with 2.35 on FF 22/23 I got same error. I'm posting a 
sample code to reproduce it:
public static void main(String[] args) 
    {
        try
        {
        WebDriver driver = new FirefoxDriver();
        driver.manage().timeouts().implicitlyWait(30, TimeUnit.SECONDS);
        
driver.get("http://shop.sonymobile.com/gb/buy/xperia-z-black/1270-5659/");
        
driver.findElement(By.cssSelector("a.cta-add-to-cart.large")).click();
        driver.findElement(By.id("cart-checkout")).click();
        driver.findElement(By.cssSelector("a.cta-button.btn-next")).click();
        Thread.sleep(5000);
        driver.findElement(By.cssSelector("p.same-as > input")).click();
        }
        catch(Throwable ex)
        {
            System.out.println(ex.getMessage());
        }
       
    }

When I click on checkbox "Same as Delivery address" I get this eror 
"org.openqa.selenium.interactions.MoveTargetOutOfBoundsException: Element 
cannot be scrolled into view"
Can anyone help me here?

Thanks
Ankush

darrell

unread,
Aug 27, 2013, 9:08:06 PM8/27/13
to webd...@googlegroups.com
Has anyone filed a reproducible defect report at https://code.google.com/p/selenium/issues/list? If no, go file one. If yes, get more people to comment on it and see if (a) you can give more insight into the problem and (b) show that this defect is affecting a number of people.

Jim Evans

unread,
Aug 28, 2013, 6:17:09 AM8/28/13
to webd...@googlegroups.com
I'll echo what you said about a reproducible case, except I'll ask please don't just go add comments to the issue to try to express it's importance to you. Extra comments on the issue report which essentially say, "Me, too, on <browser version> running on <OS version> with <Selenium version>," add next to no value to the issue report. If you don't have a reproducible case (including an HTML page or public URL to test against), it's far more effective to "star" the issue rather than add a comment. Such extraneous comments merely add noise to the issue report and make it harder for the dev team to actually get the information they need to fix the issue.

Additionally, please don't add comments to issues asking for status updates. As a developer on the project, every time I see a comment saying, "Any update on this?" the snarky jerk in me wants to reply, "Yes, there's a status update, but we aren't telling you because we don't like you." If we have a status update, it'll be in the issue report; no need to ask.

Krishnan Mahadevan

unread,
Aug 28, 2013, 3:18:43 PM8/28/13
to webd...@googlegroups.com
Jim,

Personally I completely understand how that feels. Trust me, when I who is morally and professionally responsible for all the issues that surface in the framework for which am responsible and "paid for" in my org tends to get irked at that " any updates " question I can understand your predicament for you are merely doing "us" all a big favor by helping make the IEDriver stable and robust!

^^bows ^^

Wish I had the technical expertise/capabilities to lend a helping hand :(



On Wednesday, August 28, 2013, Jim Evans wrote:
I'll echo what you said about a reproducible case, except I'll ask please don't just go add comments to the issue to try to express it's importance to you. Extra comments on the issue report which essentially say, "Me, too, on <browser version> running on <OS version> with <Selenium version>," add next to no value to the issue report. If you don't have a reproducible case (including an HTML page or public URL to test against), it's far more effective to "star" the issue rather than add a comment. Such extraneous comments merely add noise to the issue report and make it harder for the dev team to actually get the information they need to fix the issue.

Additionally, please don't add comments to issues asking for status updates. As a developer on the project, every time I see a comment saying, "Any update on this?" the snarky jerk in me wants to reply, "Yes, there's a status update, but we aren't telling you because we don't like you." If we have a status update, it'll be in the issue report; no need to ask.

--
You received this message because you are subscribed to the Google Groups "webdriver" group.
To unsubscribe from this group and stop receiving emails from it, send an email to webdriver+...@googlegroups.com.
To post to this group, send email to webd...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.


--
Thanks & Regards
Krishnan Mahadevan

"All the desirable things in life are either illegal, expensive, fattening or in love with someone else!"
My Scribblings @ http://wakened-cognition.blogspot.com/
Reply all
Reply to author
Forward
0 new messages