[ https://issues.apache.org/jira/browse/OFBIZ-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14222346#comment-14222346 ]
Jacques Le Roux commented on OFBIZ-5883: ---------------------------------------- Actually when I 1st saw your change Gareth, I thought that the line which assigns the value to the calendar should be out of the block which changes the value. Then I did not think about the slilders and removed it. It's not quite clear to me why Date.CultureInfo.formatPatterns.longTime from date.js returns ms (always .000 it seems). I don't know if this would not happen, but anyway I eventually prefer to assign the value to the calendar out of the block which changes the value. So I committed a last change in trunk r1641165 R13.07 r1641168 R12.04 r1641169 > jQuery datetimepicker popup time value is not set correctly from an existing > value > ---------------------------------------------------------------------------------- > > Key: OFBIZ-5883 > URL: https://issues.apache.org/jira/browse/OFBIZ-5883 > Project: OFBiz > Issue Type: Bug > Affects Versions: Release Branch 12.04, Release Branch 13.07, Trunk > Reporter: Gareth Carter > Assignee: Jacques Le Roux > Priority: Minor > Fix For: Upcoming Branch, 12.04.06, 13.07.02 > > Attachments: 1641119.patch > > > The jQuery datetimepicker popup for date-time fields does not set the time > correctly from an existing value. This is because all date-time (Timestamp) > fields return a millisecond component which is not supported by > datetimepicker. It seems that datetimepicker is unable to parse the time with > a millisecond component and instead defaults to 00:00 -- This message was sent by Atlassian JIRA (v6.3.4#6332)