Hi Trey, What makes you believe that the value for atCheckWaiting of a page is ignored when using it as an argument for to: configuration option of a content template? Are you seeing at check failures that do not contain WaitTimeoutException in the stacktrace? From what I can see in the code atCheckWaiting setting for a page will not be ignored in that case which makes me wonder why you believe it is.
Marcin On Thu, Apr 2, 2020 at 2:09 AM Trey Turner <[email protected]> wrote: > Hi there, > I had assumed that a content element declared with a (to:PageName) > parameter would use the target page's (or default) atCheckWaiting value, > but it seems I must also specify the toWait in each case. Is there any way > to specify a global toWait? The need for this is pervasive in my complex > SPA. > > Thanks, > Trey > > -- > 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/c863c7b9-70d3-4f4e-bd57-14cfe2d2a4b8%40googlegroups.com > <https://groups.google.com/d/msgid/geb-user/c863c7b9-70d3-4f4e-bd57-14cfe2d2a4b8%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CA%2B52dQTtXDZmjinP2rDokeC-7n0VSyO8KX1tit4j4Ng5drxBdQ%40mail.gmail.com.
