'Element is not clickable' error in chrome.

[Subrahmanyam Rentala]

Problem Statement: 'Element in not clickable error' comes while using the click action on any element in Chrome. Refer this site for more details:

https://sites.google.com/a/chromium.org/chromedriver/help/clicking-issues

How i overcome this issue ?

I used waitFor closure on click actions. This has resolved the issue.

I tried to override the click() method of NonEmptyNavigator Class, but i was unable to do that. 

Is there way that i can override this method in my Framework ?

If not, then i would like to make changes in click method by putting waitFor inside the the click method.

eg: I will replace the following code:

@Override
Navigator click() {
    contextElements.first().click()
    this
}

with 

@Override
Navigator click() {
    getBrowser().waitFor {contextElements.first().click()}
    this
}

Please suggest.

~Subrahmanyam

[Varun Menon]

Hi Subrahmanyam,

According to the link you shared the main reason behind the failure is element not clickable for the given where you are clicking.

It will be good if you change the locator to exact clickable item on the page as suggested in the link shared by you.

Your solution will have multiple implications in your execution and hence I wont really suggest it to be used:

- Increases the execution time for all the browsers.

- Any failure thrown during click action will be overridden by timeout exception.

In case you still want to go with the implementation  you can do so by implementing your own InnerNavigatorFactory as mentioned below:

https://github.com/geb/geb/blob/master/module/geb-core/src/main/groovy/geb/navigator/factory/DefaultInnerNavigatorFactory.groovy

And then configuring Geb to use your Navigator Factory by setting the property "innerNavigatorFactory" in GebConfig.groovy as mentioned below.

innerNavigatorFactory = new CustomNavigatorFactory()

- Varun

http://in.linkedin.com/in/varunmenon/en

--
You received this message because you are subscribed to the Google Groups "Geb User Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to geb-user+u...@googlegroups.com.
To post to this group, send email to geb-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/geb-user/b681b234-3734-49fb-8bae-d95488bcd254%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Marcin Erdmann]

Both Varun's suggestions are spot on.

To view this discussion on the web visit https://groups.google.com/d/msgid/geb-user/CACVPfJk-4t-cc2J0dhr5cxJrN70O08WPCK%2BA%2B-%2B72%2B%2BpNrxacg%40mail.gmail.com.

[Subrahmanyam Rentala]

Hi Varun , 

Thanks. I can try the solution provided by you.

But using waitFors {} should not increase execution time, as the moment it gets the element to be clicked, it will do its action and will come out of the closure.

Also, the solution which was provided in the link to get the exact element locator was already considered, but still the error comes. 

The waitFors {} on click has actually solved the issue in chrome, and there was no increase in the time execution as well.

What we can do is, if we do not want this to effect other browser, we can just use: 

@Override
Navigator click() {
if(driver.toString().contains("chrome")){
    getBrowser().waitFor {contextElements.first().click()}
}
else{
    contextElements.first().click() 
}
    this
}

The only reason why i am proposing this solution is any body using click actions in chrome will face this issue.

We have drastically reduced our failure count by implementing this solution, with zero side effects.

~Subrahmanyam

[Varun Menon]

Hi Subrahmanyam,

In your case there is not much extra time consumed but there is a probability of time consumption. Consider a scenario where the element is displayed after an Ajax call and we need to click on it after it is displayed. In a normal case we will do a "waitFor" element to be displayed and then call a click. If the element is not displayed in your case the code will take twice the actual time. 

Also your implementation will affect every click that you are going to do in your testcases but the said chrome issue may not be with all the elements. You can have a separate method click implemented in your base classes that you can use for such elements. 

Its your call as you know your framework and requirement better.

- Varun

To view this discussion on the web visit https://groups.google.com/d/msgid/geb-user/463fb004-8df9-4b86-befd-c5db02b4e580%40googlegroups.com.

[Varun Menon]

Sorry wrong use case about the time taken. My bad. :)

Basically the program will take the default waitFor time to click an element even when the element is not displayed.

- Varun

[Jacek Tołkanowicz]

Hi Marcin,

is there possibility that Navigator could have property isClickable() which would mean that elememnt isDisplayed and you can click it? That there is no overlay on top of it.

[Marcin Erdmann]

Everything is a possibilty, you know, Jacek. Why do you ask? Why would you need a method like that?

To view this discussion on the web visit https://groups.google.com/d/msgid/geb-user/68e63ff8-ca63-4d3a-b273-c05c9b149e64%40googlegroups.com.

[Jacek Tołkanowicz]

Currently when I login to my portal, sometimes I get advertisment which overlays login button. Currently I use this code:

waitFor(){
   loginButton.click()
}

It works but as I see in Geb source code Wait.waitFor executes click() and catches the exception thrown by Selenium. If we had sth like isClickable or isVisible that we could eliminate clicking and catching Exception from waitFor.

On the other hand Selenium probably check's this clickability/visibility underneath before executing click() so the main gain would come from not throwing (Selenium) and catching exception (Geb).

[Milosz Prymula]

You could try moving .click() outside of the waitFor clause, it works well in my project.

[Jacek Tołkanowicz]

If I move click outside waitFor I get ''Element in not clickable error'. That's the whole point of puting it in this clause. WaitFor not only checks the clause but also catches the exception, look here:

https://github.com/geb/geb/blob/847e69efb10182f859093763504117312a363e81/module/geb-waiting/src/main/groovy/geb/waiting/Wait.groovy#L124

[Marcin Erdmann]

Jacek,

I personally would not depend on there being isClickable() or isVisible() but would have code that checks if an ad is shown when loading the page and dismiss it. On one of my projects we had a problem with a cookie bar overlaying some elements on pages causing flakiness in our tests. We solved it by dismissing the cookie bar in `onLoad()` of our pages:

class CookieBarPage extends Page {

    boolean autoCloseCookieBar = true

    static content = {

        cookieBar(required: false) { $('.cookie-message.is-visible-block ') }

    }

    void onLoad(Page previousPage) {

        if (autoCloseCookieBar && cookieBar) {

            cookieBarCloseButton.click()

        }

        super.onLoad(previousPage)

    }

}

Note that autoCloseCookieBar method can be used to disable closing the bar upon page load when testing the cookie bar itself:

to(new CookieBarPage(autoCloseCookieBar: false))

....

Cheers,

Marcin

To unsubscribe from this group and stop receiving emails from it, send an email to geb-user+unsubscribe@googlegroups.com.

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

To view this discussion on the web visit https://groups.google.com/d/msgid/geb-user/a5046f05-e7f2-4135-aaf6-38bf36c51edd%40googlegroups.com.

[Jacek Tołkanowicz]

Hi Marcin,

Fair point. I also tried doing this, but this overlay (advertisement), I couldn't deactivate it in 'deterministic way'. I can try doing it once more.

Anyway waitFor works for me for now.

Thanks for this suggestion