This is a migrated thread and some comments may be shown as answers.

[Solved] IE8 regression with Q1 2010 release and Prototype (it works great with Q3 2009)

2 Answers 74 Views

Scheduler

This is a migrated thread and some comments may be shown as answers.

Abel LEITE asked on 16 Mar 2010, 04:16 PM

Hello,

I encountered a regression with the RadScheduler control when updating the dll's from Q3 2009 to Q1 2010.
I am using Prototype too (and cannot remove it).

So the problem occurs only with Q1 2010 and IE8.
I tested it with IE7, FireFox 3.6 & Chrome 5.0 and it works normally.

I created a very simple test page so you can reproduce this bug.

    
            <%@ Page Language="C#" AutoEventWireup="true" CodeFile="TelerikRegression.aspx.cs" Inherits="TelerikRegression" %> 
        
            <%@ Register TagPrefix="telerik" Namespace="Telerik.Web.UI" Assembly="Telerik.Web.UI" %> 
        
            <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 
        
            <html xmlns="http://www.w3.org/1999/xhtml">  
        
            <head runat="server">  
        
                <title></title>  
        
                <script type="text/javascript" src="prototype.js"></script> 
        
            </head> 
        
            <body> 
        
                <form id="form1" runat="server">  
        
                    <asp:ScriptManager ID="ScriptManager" runat="server"></asp:ScriptManager> 
        
                    <telerik:RadScheduler runat="server" ID="RadScheduler" ShowFullTime="True" OverflowBehavior="Expand" 
        
                        DataKeyField="ID" DataSubjectField="Subject" DataStartField="Start" DataEndField="End" >                      
        
                    </telerik:RadScheduler> 
        
                </form> 
        
            </body> 
        
            </html>

Thanks

2 Answers, 1 is accepted

answered on 17 Mar 2010, 01:55 PM

Hi Abel,

Actually the problem comes from the latest jQuery (embedded in RadControls for ASP.NET AJAX) which uses scrollTo to detect if an element is a window element. Prototype on the other hand injects scrollTo method in all elements... This is a classic example of a clash between feature detection and DOM pollution. To fix this you may replace the scrollTo method in prototype.js with for example $scrollTo. You'll have to also replace all calls to it inside prototype itself and all other libs that reference it.

Let me know if this helps.

Sincerely yours,
Kamen Bundev
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.