When using sortable on tabs there is a bug when calling tabs('remove', index) : a wrong tab is removed instead of the one at the given index.
To check this, merge the "Sortable" and "Simple manipulation" demos. Add some tabs then rearrange them a couple of times. Delete the second tab starting from left and it remains there while another tab gets deleted.
It looks like the tab order is kept into an internal array that is not affected by the sortable effect.
Is there a workaround to this before the next version as I'm now locked with this bug?
I have a problem with a page that uses intensive jQuery code.
After a little while, IE 8 uses up to 90% of the CPU and the PC is getting very slow.
Refreshing the page solves the problem, so I'm pretty sure something goes wrong with my jQuery code.
As this page binds and uses many events (onclick, onkeypress, onchange, etc), I'm wondering if there is a dead loop somewhere in the event chain, but this is pretty hard to debug as I can't find a way to reproduce the problem which happens randomly.
So I'm wondering if there is a way to trace all bound events and log them to Firebug console, even the events that I don't bind myself. That way I could see if there is a huge event log when the CPU load gets high.