Easier way to solve this would be to check for the presence of your overlay and then do a jquery.remove to just whack it altogether. Once you know it is gone then use your loginButton.click().
> On Feb 28, 2017, at 4:38 PM, [email protected] wrote: > > > [email protected] Google Groups > Topic digest > View all topics > 'Element is not clickable' error in chrome. - 1 Update > 'Element is not clickable' error in chrome. > "Jacek Tołkanowicz" <[email protected]>: Feb 28 05:15AM -0800 > > 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). > > > W dniu niedziela, 26 lutego 2017 14:51:22 UTC+1 użytkownik Marcin Erdmann > napisał: > Back to top > You received this digest because you're subscribed to updates for this group. > You can change your settings on the group membership page. > To unsubscribe from this group and stop receiving emails from it send an > email to [email protected]. -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/geb-user/2EF8989F-2C46-4477-B51D-99185715141B%40howlingdogwoodworking.com. For more options, visit https://groups.google.com/d/optout.
