This could be a couple things. Do you have *atCheckWaiting *set to true in
GebConfig? If so, it will wait for everything in your pages *static at {}*
block. The other thing could be the driver's page load strategy. I know
Chrome and Firefox drivers you can set different levels of page load
strategy with capabilities. For example, my firefox driver uses
capabilities.setCapability("pageLoadStrategy","eager")
*pageLoadStrategy* supports the following values :
1.
*normal*
This stategy causes Selenium to wait for the full page loading (html
content and subresources downloaded and parsed).
2.
*eager*
This stategy causes Selenium to wait for the DOMContentLoaded event
(html content downloaded and parsed only).
3.
*none*
This strategy causes Selenium to return immediately after the initial
page content is fully received
Be careful when you change this though as you can introduce a lot of timing
errors.
On Thursday, October 10, 2019 at 10:49:06 AM UTC-5, Ben Frey wrote:
>
> I have a logon script that goes to the login page, enters the user's
> credentials, then once we hit the member home page, I want to navigate to a
> specific URL. This works fine, but Geb is waiting for *all *of the
> content on the home page to load before it navigates away, which is
> unnecessary. Is there a way to tell Geb "once you're at HomePage,
> immediately navigate to TargetPage"?
>
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/geb-user/2880e0ce-b84d-41d3-8981-84b94d9293ba%40googlegroups.com.
