saveClientState doesn't get called by non-UpdatePanel AutoPostBack/UseSubmitBehavior=false controls



This problem should be limited to Tabs since that's the only component that relies on AjaxControlToolkit.ControlBase.saveClientState like this.
Closed May 12, 2009 at 6:40 PM by
Issue resolved in latest checked-in source code.


NWGaEagle wrote Mar 13, 2007 at 7:29 PM

An easy way to test this is to put a datagrid with edit buttons inside the second tabpanel of a tabcontainer. Clicking the Edit button fires the event, but it does not save the tab container's state.

NWGaEagle wrote Mar 13, 2007 at 7:48 PM

Sorry, clarification on that. Drop a datagrid on there and use an EditColumn with a LinkButton as the ButtonType. If you use the LinkButton it will not capture the client-side or server side event. If you use the PushButton ButtonType, it will trigger both the saveClientState and the server side event.

zati wrote May 28, 2007 at 7:26 AM

I've got the same problem. I've attached a sample. If you click on the LinkButton after changing active tab, the new state is not saved. If you click on the Button after changing active tab, the new state is kept.

MicScoTho wrote Jun 5, 2007 at 7:52 PM

As NWGaEagle suggests, this bug makes Tabs completely unusable if you want to use it with a DataGrid or GridView with edit buttons, sorting, etc.

andrewhar wrote Jul 12, 2007 at 9:12 PM

i'm getting this undesired behavior with formview.

tadams wrote Sep 6, 2007 at 9:14 PM

One thing I noticed is that the tabs.js is missing the loadclientstate function.

ttrentham wrote Mar 4, 2008 at 10:09 PM

I just ran into this myself. I guess it's still an issue and will have to be worked around?

expresso wrote Aug 14, 2008 at 4:10 AM

Why is the priority set low on this? This is a major limitation to the tab control.

veloearl wrote Feb 11, 2009 at 6:41 PM

I am running into the same limitation with a custom script control I wrote that inherits ControlBase from the Ajax Control Toolkit. My control's SaveClientState method is not being called when the form is submitted with a LinkButton. So, this is not just limited to the Tab control, but to any script controls that are developed based on the toolkit's ControlBase.

SeariderFalcon wrote Apr 6, 2009 at 7:00 PM

This bug essentially renders tabs useless without applying some sort of workaround, and it hasn't been fixed in 2 years. When I select a library for use in my production code, things like "has contained a bug for 2 years that would cause your customers to go insane" are things that I would like to avoid. I'll look elsewhere for a library that doesn't require me to write additional code (however little that code may be) to solve the defects of the library.