Thanks, JC. This is very helpful
On Monday, June 24, 2019 at 8:58:20 AM UTC-5, jc wrote:
>
> As far as I know the ExpectedCondition for waiting for an element to be
> clickable is waiting for the element to be displayed && enabled.
>
> I would imagine that just waiting for the navigator should be sufficient
> which can be done several ways. You can do this to wait for a navigator:
> waitFor{navigator}
>
> Or in your content block for the page you can put a wait on a navigator:
> static content= {
> navigator(wait: true) {...}
> }
>
>
> If you really want to replicate the Selenium wait you could create a
> method like:
> def waitForElementToBeClickable(Navigator nav){
> waitFor { nav.displayed && nav.firstElement().enabled }
> }
>
> But that really shouldn't be necessary.
>
> Just throwing some ideas out there.
>
> On Monday, June 24, 2019 at 8:40:30 AM UTC-5, Varun Jain wrote:
>>
>> Hi,
>>
>> I am looking for a method to check if the element is clickable. This can
>> be checked in Selenium through the use of ExpectedConditions but I am not
>> able to find a similar thing in Geb. Does anyone have to way to verify that
>> element is clickable
>>
>> Varun
>>
>
--
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/679b4697-98f0-42cc-a22e-f95423ca3fbc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
