Probably difficult to perceive because the user was getting into CONF-31548 first. Now that mreis fixed it, it is a good win to fix this table row deletion problem for all.

Attached two video captures. One showing the problem and the other with the possible cause: Seems like if the cell that the caret is going to get into after deleting the row is empty, the selection range doesn't get placed correctly there.