Hello. I have a problem with malformed RadDatePicker controls in my application. This problem started to occur as soon as I upgraded from Q2 2011 to Q3 2011.
The problem is that when RadFormDecorator is used on the form, the RadDatePicker/RadTimePicker ignores any Width attribute and produces a very wide textbox. If you have another control to the right of the RadDatePicker/RadTimePicker, it will superimpose over the RadDatePicker. Please see the code sample below and the two attached files.
This problem occurs in the current versions of Safari and Chrome on Windows and OS X. IE and Firefox render the controls correctly. If I modify the RadFormDecorator control's ControlsToSkip attribute to exclude textboxes, the controls render correctly in all browsers, but of course it mangles all my textboxes. My application is quite large, and as RadControls were originally applied to a legacy application, we have made extensive use of the RadFormDecorator control to pretty things up. Removing it from the application and manually applying styles to all my pages, and retesting everything is a very large task.
Other than rolling back to Q2 2011, which gives me nightmares, does anyone else have any ideas?
Here's the sample code:
The problem is that when RadFormDecorator is used on the form, the RadDatePicker/RadTimePicker ignores any Width attribute and produces a very wide textbox. If you have another control to the right of the RadDatePicker/RadTimePicker, it will superimpose over the RadDatePicker. Please see the code sample below and the two attached files.
This problem occurs in the current versions of Safari and Chrome on Windows and OS X. IE and Firefox render the controls correctly. If I modify the RadFormDecorator control's ControlsToSkip attribute to exclude textboxes, the controls render correctly in all browsers, but of course it mangles all my textboxes. My application is quite large, and as RadControls were originally applied to a legacy application, we have made extensive use of the RadFormDecorator control to pretty things up. Removing it from the application and manually applying styles to all my pages, and retesting everything is a very large task.
Other than rolling back to Q2 2011, which gives me nightmares, does anyone else have any ideas?
Here's the sample code:
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Test2.aspx.cs" Inherits="Test2" %><%@ Register Assembly="Telerik.Web.UI" Namespace="Telerik.Web.UI" TagPrefix="telerik" %><!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></head><body> <form id="form1" runat="server"> <telerik:RadScriptManager ID="RadScriptManager1" runat="server"> </telerik:RadScriptManager> <telerik:RadFormDecorator ID="RadFormDecorator1" DecoratedControls="All" runat="server" Skin="Default" ControlsToSkip="Label" /> <div> <telerik:RadDatePicker ID="RadDatePicker1" runat="server" DateInput-DateFormat="dd MMM yyyy" Width="110px" /> <telerik:RadDatePicker ID="RadDatePicker2" runat="server" DateInput-DateFormat="dd MMM yyyy" Width="110px" /> </div> </form></body></html>3 Answers, 1 is accepted
0
Hello Brett,
This is a known issue and it originates from the version 15 of Google Chrome. However, it is already fixed and is part of 2011.3.1122 version in our internal builds. You can download it (or newer) from your account or waiting for the next official version - Q3 2011 SP, which will be released in the beginning of January.
Greetings,
Milena
the Telerik team
This is a known issue and it originates from the version 15 of Google Chrome. However, it is already fixed and is part of 2011.3.1122 version in our internal builds. You can download it (or newer) from your account or waiting for the next official version - Q3 2011 SP, which will be released in the beginning of January.
Greetings,
Milena
the Telerik team
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now
0
Software
Top achievements
Rank 1
Rank 1
answered on 27 Dec 2011, 03:33 PM
Hi Milena,
Thanks for your reply, and also for being so quick at this time of the year. :)
I just wanted to point out that the problem occurs not only in Chrome (I'm using 16.0.912.63) but also in Safari 5.1.2 (7534.52.7) on Mac.
Thus it is not merely an issue with Chrome.
Thanks.
Brett
Thanks for your reply, and also for being so quick at this time of the year. :)
I just wanted to point out that the problem occurs not only in Chrome (I'm using 16.0.912.63) but also in Safari 5.1.2 (7534.52.7) on Mac.
Thus it is not merely an issue with Chrome.
Thanks.
Brett
0
Hello,
I confirm that the same problem exists in Safari, but in the pointed version of our Internal Builds it is fixed for all browsers.
Kind regards,
Milena
the Telerik team
I confirm that the same problem exists in Safari, but in the pointed version of our Internal Builds it is fixed for all browsers.
Kind regards,
Milena
the Telerik team
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now