Currently it's possible for Case instance to fire multiple resolve events. It occurs e.g. in headersAttrRefersToATableCell assessment.
You can run accessibility-tests/headersAttrRefersToATableCell.html test to experience this issue. With current master-2.2.x it will produce 16 assertions, out of 8 tables (tested elements).
Reason
The reason for this issue is $.each loop in headersAttrRefersToATableCell.js.
To understand it we need to remember that setting a case status will dispatch resolve event. In code mentioned above $.each function changes _case status for every matched header / cell. So as a result we have multiple resolve events.
We should prevent this kind of situation, or even throw an error if someone is doing so.
Currently it's possible for
Caseinstance to fire multipleresolveevents. It occurs e.g. inheadersAttrRefersToATableCellassessment.You can run
accessibility-tests/headersAttrRefersToATableCell.htmltest to experience this issue. With currentmaster-2.2.xit will produce 16 assertions, out of 8 tables (tested elements).Reason
The reason for this issue is
$.eachloop inheadersAttrRefersToATableCell.js.To understand it we need to remember that setting a case
statuswill dispatchresolveevent. In code mentioned above$.eachfunction changes_casestatus for every matched header / cell. So as a result we have multipleresolveevents.We should prevent this kind of situation, or even throw an error if someone is doing so.