I'm trying to migrate some code from 2014.2 to 2015.2. I'm using an igDatePicker. Everything works for 2014.2, but I get odd behavior with 2015.2. I don't know how to get the desired behavior. Whether I set EnableUTCDates to true or false the behavior is wrong.
To test my code I'm pointing to the lastest 2015.2 code.
Here is one scenario:
1. I set the DatePicker value to null.
2. I select date 7/1/2000 in the dropdown and that is what appears in the field for the datepicker. The calendar disappears (as expected).
3. I click the button to show the calendar again and the date is 6/30/2000, one day earlier.
Set dateInputFormat to "dateTime" I get the following result. I start with the date set to null.
1. I select date 7/1/2000. The date that show is 7/1/2000 xx:xx xx, where xx:xx xx is whatever the current time is.
2. I modify the time to be 7/1/2000 00:00 AM.
3. I click the button to display the calendar and the time immediately changes back to xx:xx xx. Not the current time, but the default time that originally appeared in step 1.
4. If I programmatically set the date to 7/1/2000 00:00 AM it shows the previous day when the calendar is displayed.
<script src="http://cdn-na.infragistics.com/igniteui/2015.2/latest/js/infragistics.core.js"></script><script src="http://cdn-na.infragistics.com/igniteui/2015.2/latest/js/infragistics.lob.js"></script>
<link href="http://cdn-na.infragistics.com/igniteui/2015.2/latest/css/themes/infragistics/infragistics.theme.css" rel="stylesheet" /><link href="http://cdn-na.infragistics.com/igniteui/2015.2/latest/css/structure/infragistics.css" rel="stylesheet" />
$("#dte").igDatePicker({ placeHolder: "Select Date...", readOnly: false, dateInputFormat: "date", enableUTCDates: true, focusOnDropDownOpen: true, mode: "editable", required: true, value: null, tabIndex: 20,
});
Hello,
Thank you for using our community.
I have created a simple sample with the configuration that you send me and the first scenario is working fine on my side. Could you try it on your side and let me know if you are experiencing the same issue. The scenario with the time that is changing every time is already fix and a build with the fix will be available on the next Service Release.
About the programmatically set data I would like to ask you, how do you set the data? Do you say what time zone to be used (like this value: "2016-01-11T17:31:10Z")? If not the editor will convert the time to the local time. Please send us more information about that scenario. We will further investigated and follow you up regarding our findings.
http://jsfiddle.net/8tsugyv7/7/
I’ll be waiting for your answer.
Best Regards, Marina Stoyanova, Software Developer, Infragistics, Inc.
I have investigates the issue with setting the date though the value method when the UTC option is enabled and it turned out to be a bug, so I have asked our engineering staff to examine this further. To ensure that it will receive attention, I have logged this behavior in our internal tracking system with a Development ID of 212365. A support case is created on your behalf with number CAS-168740-J9H0S1, so that you can be notified when the bug is fixed.
You can find your active cases under Account - Support Activity in our website. Select your ticket and go to Development Issues tab to view the status of related bugs.
Let me know if I may be of further assistance.