Element not clickable at point (X, Y) other element would recieve the click

[shan khan]

org.openqa.selenium.WebDriverException: Element is not clickable at point (573.6166687011719, 416). Other element would receive the click: <a href="/content/provider/en/secure/corporate/pages/home/help.html" aria-label="Help" ng-href="/content/provider/en/secure/corporate/pages/home/help.html" target="_self" id="mobile-menu-md-button-11" class="md-button md-ink-ripple" ng-transclude=""></a>

Command duration or timeout: 81 milliseconds

I am getting this when I am trying to click on submenu item from the Firefox browser the screen resolution is

driver.manage().window().setSize(new Dimension(750, 800));

I tried all these

WebElement element = driver.findElement(By.id(navID));

Actions action = new Actions(driver);

  action.moveToElement(element).sendKeys(element, Keys.RETURN).build().perform();

it didn't work need help on these

[Juan Luna]

Not sure with the information provided, but guessing a little I wonder one of the two cases may be the problem:

1. Click on the main menu, then click on the submenu with a delay

2. If you are already doing so, have you tried to click on the parent element?

just guessing...

Regards,
--------------------------------------
        Juan J. Luna
SQA & Process Engineer
         sapere aude

--
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.
Visit this group at https://groups.google.com/group/webdriver.
For more options, visit https://groups.google.com/d/optout.

[Madhan Gopal Reddy]

This is because selenium webdriver execute much faster than the sub-menu to appear on the screen.

Try using delay between commands(between first main menu and sub-menu) click.

maybe try Thread.sleep(1000);

[darrell grainger]

Juan hit on a key difference between Selenium 1.x (obsolete) and Selenium 2.x (webdriver). If I have a hidden element I can click on it using Selenium 1.x right away. However, in Selenium 2.x they are emulating how a user would really test it. They would go to the main menu, hover over the menu, wait for the sub-menu to appear then click the sub-menu.

Selenium 2.x needs detailed instructions to work. If you test code is just:

1. Click sub-menu

This is insufficient. You need to code something like:

1. Find main menu
2. Hover over main menu
3. Wait for sub-menu to open up
4. Find element on sub-menu
5. Click sub-menu item

This is assuming the steps to test the application are as stated. Maybe these are the wrong steps. Once you figure out ALL the detailed steps for manually testing it, then you need to automate those manual steps. Automating is easy. Figuring out what to automate is hard.

[SuperKevy]

Do we even know if the object to click actually takes a Return if its in focus?

The error message indicates the parent object takes the click: "Other element would receive the click" 

Darrell's path is a the human logical path which the tool emulates very well.