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

RadDatePicker/RadTimePicker incorrect width in Safari

4 Answers 76 Views
Input
This is a migrated thread and some comments may be shown as answers.
Mark DeMichele
Top achievements
Rank 1
Mark DeMichele asked on 04 Jun 2008, 03:39 PM
Hi,

I have several RadDatePicker and RadTimePicker controls where I specify a width of 100px. Safari Mac and Safari PC is not recognizing this width while other browsers do. If I inspect the input field in Safari, it has a width of 149. This shows up under "computed styles." Is there a fix or workaround for this?

Thanks,
Mark

4 Answers, 1 is accepted

Sort by
0
Konstantin Petkov
Telerik team
answered on 05 Jun 2008, 06:56 AM
Hi Mark,

We must admit about this problem in Safari, but I believe we managed to resolve it for the latest official update, labeled 2008.1.515. The input width seems to be correct on the online demos too:

http://www.telerik.com/DEMOS/ASPNET/Prometheus/Calendar/Examples/Design/Sunny/DefaultCS.aspx

Let us know if further assistance is needed.

Greetings,
Konstantin Petkov
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center
0
Mark DeMichele
Top achievements
Rank 1
answered on 05 Jun 2008, 03:56 PM
Thanks. Updating to the latest version did not help. I found the solution though.

If the RadDatePicker, RadTimePicker, or RadDateTimePicker's container element has white-space=nowrap or nowrap, the width isn't recognized in Safari. I confirmed this with Table, Td, and Div. Taking out the nowrap allows the width to be recognized.
0
Konstantin Petkov
Telerik team
answered on 06 Jun 2008, 10:07 AM
Hello Mark DeMichele,

I tried the latest 2008.1.515 version once again and the pickers width is respected. Since there is a problem with the TimePicker in Safari though (introduced in the latest version) I have attached an example with the latest internal build as well. Please, give it a go and let us know if it helps.

All the best,
Konstantin Petkov
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center
0
Konstantin Petkov
Telerik team
answered on 06 Jun 2008, 10:14 AM
Hi Mark DeMichele,

This is just a quick follow-up since it seems I've omitted an important part of your description. We managed to replicate the problem and will investigate it as soon as possible. Hopefully we will manage to include a bug fix officially for the next Service Pack expected in two weeks.

All the best,
Konstantin Petkov
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center
Tags
Input
Asked by
Mark DeMichele
Top achievements
Rank 1
Answers by
Konstantin Petkov
Telerik team
Mark DeMichele
Top achievements
Rank 1
Share this question
or