[arquillian-issues] [JBoss JIRA] (ARQGRA-479) Propagate xhr.response values in wrapper callback

[Lukáš Fryč (JIRA)]

     [ https://issues.jboss.org/browse/ARQGRA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lukáš Fryč updated ARQGRA-479:
------------------------------
              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/137, https://github.com/arquillian/arquillian-graphene/pull/138


> Propagate xhr.response values in wrapper callback
> -------------------------------------------------
>
>                 Key: ARQGRA-479
>                 URL: https://issues.jboss.org/browse/ARQGRA-479
>             Project: Arquillian Graphene
>          Issue Type: Bug
>    Affects Versions: 2.0.3.Final, 2.1.0.Alpha2
>            Reporter: Lukáš Fryč
>            Assignee: Lukáš Fryč
>             Fix For: 2.0-Tracking, 2.1-Tracking
>
>
> When the xhr wrapper is created the response property is copied but it isn't updated in the callback, which leads to the property values' being out of sync. Some frameworks (e.g. Angular) will use the xhr.response over xhr.responseText if it is present, which means that simply using a guardAjax in a Graphene test will cause all subsequent xhr calls to return invalid data. In my case (Firefox 38, Angular 1.4.4, Graphene 2.0.3.Final) all $http calls would return "" once a guardAjax was executed, despite valid data being shown in Firefox's request log.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)