[
https://issues.apache.org/jira/browse/OFBIZ-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14222909#comment-14222909
]
Gareth Carter commented on OFBIZ-5883:
--------------------------------------
UK Date.CultureInfo.formatPatterns.longTime is HH:mm:ss, I believe both datejs
and jquery datetimepicker don't support the ms part and both fail to parse the
value properly if it does exist. The actual ms value is coming from ofbiz not
datejs or jquery.
The only reason I put it in the if block is because it identifies a change in
the value.
> 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)
