You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
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.
The text was updated successfully, but these errors were encountered:
Currently it's possible for
Case
instance to fire multipleresolve
events. It occurs e.g. inheadersAttrRefersToATableCell
assessment.You can run
accessibility-tests/headersAttrRefersToATableCell.html
test to experience this issue. With currentmaster-2.2.x
it will produce 16 assertions, out of 8 tables (tested elements).Reason
The reason for this issue is
$.each
loop inheadersAttrRefersToATableCell.js
.To understand it we need to remember that setting a case
status
will dispatchresolve
event. In code mentioned above$.each
function changes_case
status for every matched header / cell. So as a result we have multipleresolve
events.We should prevent this kind of situation, or even throw an error if someone is doing so.
The text was updated successfully, but these errors were encountered: