ASP.NET Ajax Control Toolkit in different browsers

This toolkit seems to be incredible, better than a lot of packaeg offered (charged) by 3rd providers. I am only concerned all these controls will behave accordingly in any browser chosen, from IE 6, 7 to Firefox. Has anyone done tests, or used them in production?

I have tested most of the controls, and use them in my production environment, with many browsers (FF 1.5(OSX, Windows), FF2(OSX, Windows), IE 6, IE 7, Opera 9(OSX, Windows), Safari (OSX)). They all worked fine. Microsoft has gone through alot of trouble to see that they do. :)

This is nice to hear, if you dont mind, a nice list table with the results of your findings with respect to the various browsers.

I am working on creating webparts ( custom composite controls , DLLS , what ever you call them) to use AJAX.NET extensions and the "unsupported" Ajax.NET ControlToolkit and I must say the behaviour is NOT as rosy as it may be when using the controls in the WYSIWYG drop-n-drop way of the VS designer.

behaviour varies from IE6 to IE7, even on mozilla

You talked about "drag & drop′", considering u r working with webparts. Actually I know there is one of the toolkit components that is able to be dragged, the others AFAIK are not able to such a task. So as for this problem you mentioned, you were referring particularly to this case with webparts ?

Hi,

When developing webparts as custom composite or server controls, drag-n-drop is not an option as the WYSIWYG editors such as VS2k3 or WS2K5.

And yes, I am referring specifically to WebParts using ASP.NET 2.0 WebParts class and also using AJAX.NET extensions and AJAXControlToolkit extenders etc.

To be clear i am talking about the behaviour of coded webparts ( not user controls such as ASCX stuck into a webpart zone) such as overriding CreateChildControls and RenderContents or Render where the layout and lifecycle of the objects are different when laying out objects on an ASP.NET webpage or webpartpage.

Anyways, its an uphill battle. Right now I want the AlwaysVisibleControl Extender ( if thats the "correct" name) to work properly in a custom ajaxified webpart (DLL). This is where the browse side problem appears.

This is why I createdhttp://forums.asp.net/t/1128326.aspx a while back with no feedback from anyone. Oh well, i will figure it out eventually.