1. Home
  2. Forum
  3. ASP.NET MVC - EJ 2
  4. EJ1/EJ2 DateRangePicker: The calendar takes time to appear

EJ1/EJ2 DateRangePicker: The calendar takes time to appear

Hi,

We have an ASP.NET MVC 5 application with EJ1 installed on it.
Recently, we've also installed EJ2. So now we have EJ1 and EJ2 loaded on each page. (We can't remove EJ1 for legacy reason).
We've added an EJ2 DateRangePicker on a page and we've noticed that there's a bit of delay (about over 1 second) between the moment we click on the icon and the moment the calendar is displayed.
We suspect that there are some EJ1 codes (inside the library) that are still triggered when we click on the EJ2 datepicker and that might be the reason of the delay.
Could you help us on that?

Thanks

5 Replies
SP Sureshkumar P Syncfusion Team February 25, 2020 12:13 PM UTC

Hi Arcania, 
 
Greetings from Syncfusion support. 
 
Based on your shared information, we have created the sample EJ1 and EJ2 daterangepicker components. we suggest you ensure whether you have referred compatibility script and CSS files for EJ1 and EJ2 components.  
 
 
Please check the sample here:  
 
If still issue persists, please share the below details to proceed further. 
1.     Share the Syncfusion component lists you have used in the same page daterangepicker used. 
2.     Share the issue replication steps or video demonstration. 
3.     If possible, please replicate the issue with our attached sample and revert with detailed issue replicate steps. 
These details are help us to provide exact solution at earliest. 
 
Regards, 
Sureshkumar P 


SA Support Arcania March 4, 2020 11:49 AM UTC

Hi,

Thanks for your reply.

1.     Share the Syncfusion component lists you have used in the same page daterangepicker used.
EJ1 dropdown, EJ1 autocomplete, EJ2 daterangepicker, EJ2 grid.

3.     If possible, please replicate the issue with our attached sample
We've added a daterangepicker on the page and we got the same issue.

---------------------------------------------------------------------------------------

We've further investigated the problem and we noticed that it depends on the machine and the browser.
(Machine_1: less powerfull, Machine_2: more powerfull)

Machine_1 / Chrome:
We get this error in the console:  [Violation] 'mousedown' handler took 786ms

Machine_2 / Chrome
We get this error in the console:  [Violation] 'mousedown' handler took 43ms

Machine_1 and Machine_2 / Firefox:
No warning and no perceptible delays.


Thanks




SP Sureshkumar P Syncfusion Team March 5, 2020 09:20 AM UTC

Hi Arcania, 
 
Thanks for your update. 
 
The violation time may differ based on system and browser configuration. So, please share the below details for further investigation. 
1.     Share the device configurations (less powerful and more powerful) 
a.     RAM details  
b.     Processor details  
c.      OS details  
2.     Share the browser version details  
a.     Less powerful machine chrome version  
b.     More powerful machine chrome version  
These details help us to provide the exact solution at earliest. 
 
Regards, 
Sureshkumar P 


SA Support Arcania March 6, 2020 05:48 AM UTC

Hi,

Here are the machine details:

Machine_1 / desktop (where we have the delays)
RAM: 16gb
Processor: Intel Core i7-7700 CPU @ 3.60GHz 3.60GHz
OS: Windows 10 64-bit
Chrome version: 78.0.3904.97

Machine_2 / laptop (where we have just 33ms delay)
RAM: 16gb
Processor: Intel Core i7-8550U CPU @ 1.80GHz 1.99GHz
OS: Windows 10 64-bit
Chrome version: 80.0.3987.116

SP Sureshkumar P Syncfusion Team March 11, 2020 01:45 PM UTC

Hi Arcania, 
 
Thanks for your update. 
 
We have checked the same scenario with your mentioned machine details. But we ware unable to replicate your reported issue. This issue raised because of local system CPU usage. So could you please ensure your machine CPU usage and please check the sample after clear the CPU usage of your machine 1 (issue reproduced desktop machine) 
Regards, 
Sureshkumar P 


Loader.
Up arrow icon