The loop is reversed because the actual targeted element (which, as far as I can tell with QUnit, there is only ever 1 of) is the last element child.  I think at the time (late at night), I was thinking reversing it would therefore be better because the element would be updated sooner... but now that I think about it in the daytime, I suppose the reflow doesn't happen until after the whole loop is completed anyway.

Ideally, I'd prefer to axe the loop altogether and just use `lastElementChild` but oldIE would need additional attention since they didn't support that till IE9.  It would also make this code more brittle if QUnit core ever decides to change their markup order/structure for test case output.  Thoughts on that?