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

[ https://issues.jboss.org/browse/ARQGRA-297?page=com.atlassian.jira.plugin... ] Lukáš Fryč edited comment on ARQGRA-297 at 4/29/13 2:28 AM: ------------------------------------------------------------ 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/g...]. 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: {code} waitModel().until().element(logout).is().present(); {code} 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)}}. was (Author: lfryc): 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/g...]. 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)}}. -- 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