[arquillian-issues] [JBoss JIRA] (ARQGRA-297) Unable to access to WebElement after HTTP request

[Lukáš Fryč (JIRA)]

    [ https://issues.jboss.org/browse/ARQGRA-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770588#comment-12770588 ] 

Lukáš Fryč commented on ARQGRA-297:
-----------------------------------

This issue is likely caused by a fact that {{guardHttp}} waits for a HTTP request and subsequent [document readiness|https://github.com/arquillian/arquillian-graphene/blob/master/graphene-webdriver/graphene-webdriver-impl/src/main/java/org/jboss/arquillian/graphene/guard/RequestGuardFactory.java#L152].

In case the document becomes ready in a second step (as illustrated by {{seq2.png}}) then {{guardHttp}} won't work,
because it will not ensure full application readiness.

----

I suggest to do not use {{guardHttp}} here, but rather more accurate condition:

waitModel().until().element(logout).is().present();

unfortunately this feature is not available in Graphene now (ARQGRA-296)

but you can simulate it using by implementing own {{Predicate}} and {{guardModel().until(Predicate)}}.
                
> Unable to access to WebElement after HTTP request
> -------------------------------------------------
>
>                 Key: ARQGRA-297
>                 URL: https://issues.jboss.org/browse/ARQGRA-297
>             Project: Arquillian Graphene
>          Issue Type: Bug
>    Affects Versions: 2.0.0.Alpha4
>         Environment: Fedora 16, Firefox/Chrome
>            Reporter: Sona Jamborova
>            Priority: Critical
>         Attachments: seq1.png, seq2.png, seq3.png
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira