We have tried to find a reason for this in DotNetNuke/CSS but has not been able to do so. Also, everything seems to be working fine in IE, Opera etc. so this seems like either a bug in Telerik (or MS Ajax) or FireFox, or the combination of the two. This assumption is based on the fact that it seem to work in most other browsers, so it is unlikely that this should be due to a design error in the web application itself, or do you disagree?
Something that would be really helpful would be if you could write (or point me to if it already exists) a "How to integrate Telerik into DotNetNuke". We've looked at http://www.telerik.com/help/aspnet-ajax/what-is-dnn.html
but it doesnt seem to do more than scratch the surface on that subject when you are a full Telerik customer (ie not just using the Telerik components distributed with DotNetNuke). Some of the unanswered questions I feel are:
- Should you replace the default ScriptManager with RadScriptManager? Pros/cons?
- Should you use the Form.Controls.Add(New Telerik.Web.UI.RadStyleSheetManager()) to register the RadStyleSheetManager or is it enough to just drag and drop a RadStyleSheetManager on the user control?
- How should you setup your DotNetNuke modules, with regards to Telerik? Should the DotNetNuke.Framework.AJAX.RegisterScriptManager() be used?
- Should you use the "supports partial rendering" on the module definition of the module (which wraps the entire module in an updatepanel) or should that he avoided when using Telerik equivalents (I assume so but still)