I'm working with a case where the text for the tab label is already HTML formatted. The TabStrip is bound to a DataSource object, allowing me to specify the text and value fields. However, I cannot specify whether the title is encoded or not.

Currently, the workaround is to use javascript to modify the HTML of the tab label after it has been rendered (http://dojo.telerik.com/UXuTE), but having a way to specify which data field to map to the encoded property would be much simpler (see above dojo for and example).

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.

Currently the tabstrip just magically selects which container element goes with which tab.

You should be able to specify it both with data- and with dataSource data so that you can tell it exactly which one to use (and can then have multiple tabs with the same content as well).

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...

At the moment, the tab strip renders the classes and elements that provide the scrollable functionality only on initial render.

Changing this configuration should be possible through the .setOptions() method, something like: https://dojo.telerik.com/@bratanov/EwoXAJuB

TabStrip should have the option to have closeable and sortable tabs.