If autopostback = 'false', then javascript doesn't work in all tabs properly, especially if the tabs are static, but if autopostback="true", then then switching between tabs takes an increasing amount of time (10 seconds or more when you get to 3 tabs created). So, that is unacceptable too. So, what is another option that I can try to resolve the ultrawebtab problems? In one of the tabs is a tree control, so, not sure if that is affecting it?
Thanks.
Hello,
Yours JS code doesn`t work because of differences in browsers or some other reason. Concerning to time increasing reason can be in that you have too much elements in each tab or something else. Could you please send a little bit more information about the HtmlEditor declaration. ASPX declaration, code-behind or sample project – anything that can get us started is welcome. There can be many reasons for that issue.
Thanks for getting back to me. We'll email you some of the code, so you can take a look at what we have done. Basically, I believe we need autopostback=true, but it's very slow, and slowing down significantly (10 seconds or more added on to load time every time you add a new tab with the user control in it. There is not many controls on the actual user control (about 10 text boxes), and there is no data in them, as it's a data entry screen only.
I put the whol webtabpanel thing in its own update panel and set it as conditional then edit any triggers i needed to fire the update. and WARP is WebAsyncRefreshPanel... which is basically Infragistics update panel. Also I am using version 2008 3 whether that has anything to do with it I dont know because I upgraded from 2007 1 to 2008 3.
Thank you. Did you have any code samples to post?
No everything I did was all in the properties of the update panel and the WebTab things. It could be that I'm displaying far less data than you are since my tabs only have grids in them with a max of 5 rows each at any given time that putting the whole WebTab in the update panel fixed the time issues I was having.
Ok, so all you did was put the webtab inside the update and that fixed the problem right away? No other code was neede to add to handle this change?
I just realized that it's already inside an update panel, and it's still slow. any other ideas?
Ahh well then I don't think I am much more help. As I said it could be the fact that I'm only displaying a small amout of data at one time that my tabs dont take long. I think the largest any of my grids get is 4 rows and even then thats rare.