If there is an event handler attached to a row element or any of its children, it is loosen when sorting occurs. Rows are cloned in the process (empty/append).

Then i tried using tablesorter widget to add handle. That the weird side: the event handler is now called several times (as many as there has been sort on the table).

I even tried to hack the plugin to add an unbind widget before sorting. I worked for unbinding on row children events, but not on the row itself.

Those rows have id attribute and that might raise some conflict.

I'm not sure if the same handler is called several times on the same element or if there ares several clones responding to the event and thus memory leaks.

Currently i had to workaround by watching event.timeStamp in the handler and discard duplicate.