This exact issue has been already discussed before with woritem [16321](https://ajaxcontroltoolkit.codeplex.com/workitem/16321). I was not able to find any other recent discussion about it.
I invite to read that report because symptoms are very well explained by the author.
I updated toolkit version from 30930 (Sep 2009) to 7.1213 (Dec 2013) on a project containing a complex implementation of TabContainer. Before the update I had no issue at all with that page and TabContainer in general, but as soon as I referenced new toolkit version I found out some strange behaviors.
I reduced it all in a very simple, standalone page, attached to this post.
Basically what happens is that when you set one or more tab to be invisible (no matter whether you do it by the attribute on tag declaration or in the code-behind), TabContainer starts to display mixed-content tabs after ActiveTabChanged event, when index requested is equals or greater than the one of the not visible.
Page attached shows it very clearly.
Note: none of the workarounds proposed in the old workitem is working in my environment.
Target framework 3.5, Toolkit version 7.1213, IIS 7.5, Windows 7 64 bit
Comments: Just ran into same issue. Please keep thread running and post any updates. Will try Asimov's work around. Very uncomfortable with a client side solution. Hope content of non-visible and non-enabled tab panels will not be visible by looking at page source or browser debugger. If so will not be a solution. Disabled tabs have sensitive data. Thanks to all in advance.
I invite to read that report because symptoms are very well explained by the author.
I updated toolkit version from 30930 (Sep 2009) to 7.1213 (Dec 2013) on a project containing a complex implementation of TabContainer. Before the update I had no issue at all with that page and TabContainer in general, but as soon as I referenced new toolkit version I found out some strange behaviors.
I reduced it all in a very simple, standalone page, attached to this post.
Basically what happens is that when you set one or more tab to be invisible (no matter whether you do it by the attribute on tag declaration or in the code-behind), TabContainer starts to display mixed-content tabs after ActiveTabChanged event, when index requested is equals or greater than the one of the not visible.
Page attached shows it very clearly.
Note: none of the workarounds proposed in the old workitem is working in my environment.
Target framework 3.5, Toolkit version 7.1213, IIS 7.5, Windows 7 64 bit
Comments: Just ran into same issue. Please keep thread running and post any updates. Will try Asimov's work around. Very uncomfortable with a client side solution. Hope content of non-visible and non-enabled tab panels will not be visible by looking at page source or browser debugger. If so will not be a solution. Disabled tabs have sensitive data. Thanks to all in advance.