Hi
I am using webdropdowns in a page. While page loading first all the controls loaded and shown to user fastly other than webdropdowns. After 2-4 secs(After all others controls loaded) only, the webdropdowns visible to the user. Why it is slow while loading? I think the webdropdowns are hidden or some bugs in it. Can you please resolve this issue in webdropdowns? Give me the solution to fix this? Urgent.
Thanks.
Sridhar
Hi Sridhar,
Could you tell me what's your setting for EnableAutoFiltering? Is it set to "Off" or "Server" ? How many items do you have in the WebDropDown? Also, which build number do you use?
Thanks,
Angel
The default is Off. You shouldn't get any slowdown on the client, because items are loaded lazily, so only the HTML that's sent can make the browser render slower. Only if it is Client, all items will be created initially on the client and it will be slower.
How many items do you have ?
EnablePaging=true, or EnableLoadOnDemand=true will certainly make a difference.
Hi Angel,
I dint set this property yet. Can I set this to off/Client? It has only 10 items. I don't need paging(why for 10 items?), load on demand binds only when the action done(I think not necessary for 10 items). The current value also coming very slowly. The user may think that the items is not available in its place for 2-4 secs.
Thanks
I have about 35 webcombo in my webpage the page takes about 30 seconds to load. If I use asp DDL, its about 3 seconds. Without any data attached to the combo its takes 22 seconds. During load I see the combo as below and each of the combo fixes itself one at a time. I think initialize takes long time. I'm using bit older version "7.1.20071.40". Any fix available for this?
Hai
Great. Works now in 9.2 version. Thanks.
yes it is released.
Did the fixed issue version released or not? This is to remind you. I am waiting for the solution.
Internal bug 22504 has been logged and I have already fixed it. Again, this is not directly related to the performance itself. I will let you know additionally in which Service Release you can expect the fix to be.