ansaurus

Question

Answer 1

A:

Check the DocType. Here is what I have found useful

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" >

Place this in your user control (or the page that uses it) and all should be well. I had a similar problem with a collapsible extender and this worked for me.

Edit: Here is a link to my question for further details.

Craig 2008-09-11 20:42:28

Answer 2

A:

I don't know if this helps, but I had the same problem with the autocomplete extender and determined that the server-side function could not be in the user control, but needed to be on the page (or in a webservice, I guess). Once I moved the function, it worked fine.

Jason 2008-09-12 15:04:14

Answer 3

A:

Hmm all that functionality on the loose! careful you don't lose it (sorry!)

Are you using something like Firebug (firefox plug-in) so you can see what ajax calls the page is trying to make? If it is making the call but the server is behaving oddly then you will see the error there too. IE users maybe able to use dev toolbar.

Aidan 2008-09-12 15:15:27

Answer 4

+1 A:

Apparently EO has compatibility issues with MS Ajax Control Toolkit. http://www.essentialobjects.com/Forum/Default.aspx?g=posts&t=1319 I guess I'll leave this question open to see if anyone figures out some sort of workaround.

Cptcecil 2008-09-12 17:27:40

Answer 5

+1 A:

After a few days of looking I found a call to a modal popup extender .show() in the code behind. After commenting it out everything worked fine.

Cptcecil 2008-09-17 12:43:49

ansaurus

tags:

views:

answers:

AJAX Dropdown Extender Question

related questions