When a tab in TabStrip is dragged out of the tabgroup, a new window containing the tab's content will be shown. When the titlebar of the window is dragged back to the tabgroup, the tab returns and the window destroyed. Something like Google Chrome's tabs.

As per Kamen's request in the support ticket (657521), I'm raising this request to change behaviour of the tabstrip widget.

At this time, when tab content is loaded through Ajax which may result in an error (either transport error, but optionally also javascript generated errors), tabs remain frozen and we can no longer click another tab to load that content.

We would like this behaviour to be changed:

a user should ALWAYS be able to click any tab available to him (we don't want the freezing at all) because we don't want to force the user into a waiting modus just because he clicked a wrong tab first.
When a user clicks a second tab, while the content of an earlier clicked tab was still loading, the widget should automatically kill the ajax call to prevent a high load on the server.

Also, we would like an option which disabled caching of tab content; if caching is disabled, we want the content of the tab reloaded each time a tab is clicked (now it gets loaded once, and we need to refresh the entire page if we want to refresh the content of one specific tab (unless we add a button somewhere to allow the user to lick "refresh"; it would be a nice option if this can just be configured at initialisaing of the tabs...

Now 

tabstrip.append({
  ..
  content: <SHOULD BE PLAIN TEXT HTML>
});

It makes more sense and adds flexibility (preserving handlers and dynamic things) to pass ready dom, rather than vapid html string.

Simply allow the tabs to be position away from the content holder, as if they were a menu.
I want the functionality of the tabs, i.e. load all controls at page load, but the feel of a menu.

Allow to edit tab(TabStrip) header name directly like when I double click or right click on any tab I can edit its name and on lost focus event it should save in database directly.

The TabStrip loading from Ajax (LoadFromContent) only supports GET method.   This is shortsighted as quite often some content needs to be delivered via HttpPost.   For the MVC component it should also support sending the model (so a partialView can be returned from the Controller).