I just upgraded to Aggregator 6.0 from 5.06 and am using DNN 4.09.04. Now when I load a page with tabs, if I am using FF or Chrome, the tabs seem to lag in loading and will show the content all over the place for a few seconds. When using IE this doesn't happen at all. Which is weird since IE is usually the problem. Does anybody know what this might be about? I was considering reinstalling the version 5.06 of Aggregator just to test, but am afraid I might really mess something up.

Hi Nathan,

Please don't downgrade. That's going to mess you up even more.

Do you have a url where I can take a look?

Hi Richard,

I sent you an email with the url and some test login information for the slow loading tab problem I'm experiencing.

Let me know if there is anything else you need.

Thanks,

Nathan

Hi Nathan,

Thanks for the login information to your site. There are a couple factors that I think are affecting the tab loading time in your case. The first is the number of tabs. In your case there are 9 primary tabs with each of them having between 4 and 6 sub tabs. Each of the sub tabs looks like it has a module embedded in it so there is a lot of content loading. The second factor I think is the jQuery tabs themselves. The jQuery tabs are triggered to load once the DOM is ready. In previous incarnations of Aggregator, including the non jQuery tabs I'm using a slightly different mechanism to load the tabs which may result in one loading slightly quicker than the others.

You may want to try one of the other tab skins such as Simple/Top for example and see if you see an improved difference.

Hi Richard, Ok, that helps. Its true I have a lot of tabs and I am loading a lot of information on to the page. In general I understand the slow load time due to the amount of content, but previously it all loaded at once versus the tabs coming in close to last. One thing I saw in another tab application that used the jquery ui was the ability to make it so that the wrapped module didn't load unless the tab was activated. That might assist in this type scenario. Any plans to develop this type of functionality? At any rate, thanks for looking into it, it is helpful to know that I didn't just have something messed up. -Nathan