Ajax Tabs bug (#4451) patch is good
On 1.7.2, I was observing the behavior mentioned in the bug's comment:
Similarly, if the ajax request takes a long time, the user may click on a different tab. This causes the same behavior described for the error case -- the slow-loading tab becomes selected when the user clicks the next tab, the content is not loaded (so you end up with a blank panel), and the tab clicks become off-by-one in the stack of clicks.
This made the tabs effectively useless for a production app, as it is almost inevitable for the user to click on a tab while another is loading, and this puts the whole tabs control into a bizarre and confusing state.