Datepicker bug in Chrome 26?

[Wendelstam]

Hi.

I have an web app that are using a datepicker and it has started to run really slow after the first postback.
I found that the "slowness" only occured in Chrome 26 (26.0.1410.43). The same code worked perfectly in Chrome 25 (verifed on another computer and slow after upgrade to 26). 

Any ideas what can cause this issue?

EDIT;
I having problems recreating the issue in a standalone project that I can post. (It is part of a large webapp). And it seems like its only a problem when the DOM is larger. I.e the example apps seems to run a little slower, but on my app it takes 3+ seconds plus to change the month in the calendar.

The thing I dont understand is that it works without any errors but its slow and only in Chrome 26+, the bottleneck seems to be located in the JS function Telerik.Web.UI.RadCalendar._navigatePrev/XXXX and its much slower after a postback.

EDIT 2:
The row that seems to take longer time is this.RenderViewDays(d, b, a, this.RadCalendar.get_orientation(), this.StartRowIndex, this.StartColumnIndex);

Any ideas why a postback could change the performace of the line above? I have stepped through the code and profiled it without finding any reason or bottleneck "hotspot".

When stepping through the code no errors or external (non-telerik-functions) gets invoked nor is any other client side functions attached.

The exact same code works perfect in other browsers (and earlier Chrome versions < 26).
 

[Eyup]

Hi Johan,

I have already replied to your support ticket 679489. I was able to reproduce the described issue and forwarded it to our developers.

Thank you for reporting it to us. Please excuse us for the inconvenience caused.

Kind regards,
Eyup
the Telerik team

[Joel]

I have the same issue....have a page with several Rad Date Pickers and Time pickers and after the first postback the delay to show the calendar popup is really bad...it seems this is only happening in Chrome. Tried safari, opera, IE 9 and 10 and Firefox and everything is fine.

Any ideas/updates on this ??

Regards!!

[Wendelstam]

Hi, there are indeed a bug in Chrome but its still not corrected, see the attached links for the threads I found about this issue.

My tests with different browsers:
Chrome version 26.0.1410.64 m = PROBLEM
Chrome 27,Canary (Windows) = PROBLEM
Chrome 27 (MacOS) = PROBLEM
IE = OK
Firefox = OK
Opera = OK
Safari (MacOS) = OK

Chromium thread/bug:
https://code.google.com/p/chromium/issues/detail?id=230504

Forum post at Telerik:
http://www.telerik.com/community/forums/aspnet-ajax/calendar/datepicker-bug-in-chrome-26.aspx

[Eyup]

Hello Joel,

You can also check out the following sticky thread which explains a possible reason for the problematic behavior:
http://www.telerik.com/community/forums/aspnet-ajax/general-discussions/google-chrome-26-performance-issue.aspx

Regards,
Eyup
the Telerik team