I have a tabstrip with two buttons -- call them A and B.  The content of tab A lets the user click on a button and go to another view, and a back button appears.  

If the user then clicks on tab B, and then on tab A, the content of tab A should still show the second view with the back button (this is how native tabstrips work).   But that isn't happening -- the view gets changed to the initial view of tab A, forcing the user to re-navigate to where they were before.

How do i make it work so that the view in each tab is preserved when a user clicks a different tab button and then back again?

Hello Ryan,

Thank you for contacting us - indeed, the native tabstrips behave in the way you describe. Each tab maintains its own stack of views. 

I am afraid that such behavior can't be accomplished with the current widget, as it would require a fundamentally different approach - each tab should have its own pane with a separate set of views associated. This would also affect the browser back button and history manipulation, to name a few things.

Given that, introducing such behavior to the current tabstrip widget would be a huge breaking change (the markup should be updated) - I think that at some point we may consider implementing this as an extension of the splitview (which maintains multiple panes), or as an entirely new widget. 

Regards,
Petyo
the Telerik team

That is unfortunate, as the point of kendo mobile is to provide as much as possible the same experience you would get in a native app.  History should be isolated to each tab and never should it be the case that hitting a back button brings you to another tab.  

Hi Ryan,

Changing the current implementation will result in a top level breaking change. We do agree that the behaviour which you described is closer to the native one, however we want to gather more information about the community interest in it.

We will appreciate if submit this as a feature request at KendoUI UserVoice portal. In this way the other users will be able to vote for it. If it gains popularity we will consider it for one of the future releases.

Kind regards,
Alexander Valchev
the Telerik team