Buggy DatePicker Button

[Developer]

Hi.
I am using the RadDatePicker and RadCalendar in a project and I noticed a bug with the datepicker button.

When I press the button in the date picker, and finish making my date selection, the datepicker button shifts down a couple of pixels.

I tried checking the margins and the z-index, but it did not really change the code much.

Here's the the code snippet.

<telerik:RadScriptManager ID="RadScriptManager1" runat="server"></telerik:RadScriptManager>    <!--needed for telerik:RadCalendar-->
    <telerik:RadAjaxPanel ID="RadAjaxPanel1" runat="server">
        <telerik:RadDatePicker ID="RadDatePicker1" runat="server" Skin="Santrio" EnableEmbeddedSkins="false">
            <Calendar ID="Calendar1" runat="server" EnableKeyboardNavigation="true" />
        </telerik:RadDatePicker>
    </telerik:RadAjaxPanel>

You may notice that I am calling a customized skin called "Santrio", but it is just the default skin, happened to be in CSS.

How do I fix this issue? Thanks!

[Princy]

Hello Michael,

I was unable to reproduce the same at my end. Are you able to reproduce the same in the online demo.
Calendar / DatePicker/First look.

Thanks,
Princy.

[Kevin]

Hello Michael,

I've noticed the same thing with the latest version of the controls when viewed in Chrome.

http://demos.telerik.com/aspnet-ajax/calendar/examples/datepicker/custompopup/defaultcs.aspx

I'm assuming it's some new bug introduced by the latest version of the controls.

[Galin]

Hello,

This issue is already fixed and will be available in the next internal build (which is to be uploaded next week).

In the meantime could you use the following CSS workaround:

@media screen and (-webkit-min-device-pixel-ratio:0)
{
    .rdfd_
    {
        position: absolute;
    }
}

Please excuse us for the inconvenience this might have caused you.

Regards,
Galin
the Telerik team

[Developer]

Thank you!

some CSS wizardry happened (similar to below) and it's resolved.

Thanks anyways for your inputs!

[Developer]

Thank you!

some CSS wizardry happened (similar to below) and it's resolved.

Thanks anyways for your inputs!