A data corruption bug in fact!

The last two days have seen a few emails roll in regarding mysterious bugs where table rows and columns would jump about randomly. The problem was that Rails allows an object to have destroy called on it twice. And it would then execute any callbacks… twice. This meant that a bunch of headers would end up with the same position value (since that was updated as a callback). This was most unfortunate, and once fixed should keep the problem from cropping up again!