[
https://issues.apache.org/jira/browse/OFBIZ-9380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025627#comment-16025627
]
Chuck Kosta commented on OFBIZ-9380:
------------------------------------
It seemed to be a pattern following issue. All the other widgets had
formName="EditFacilityForm" so we used it in the date picker. However, if you
leave formName="" empty; then it works...
The question is whether 'EditFacilityForm' is supposed to be there or not?
If you add this code below to your EditFacility page 'as is' let me know what
happens.
{code}
<@htmlTemplate.renderDateTimeField name="closedDate" event="" action=""
className="" alert="" title="Format: yyyy-MM-dd HH:mm:ss.SSS"
value="${facility.closedDate!}" size="25" maxlength="30" id="closedDate"
dateType="date" shortDateInput=false timeDropdownParamName=""
defaultDateTimeString="" localizedIconTitle="" timeDropdown="" timeHourName=""
classString="" hour1="" hour2="" timeMinutesName="" minutes="" isTwelveHour=""
ampmName="" amSelected="" pmSelected="" compositeType=""
formName="EditFacilityForm"/>
{code}
> renderDateTimeField works in IE, not working with lastest Chrome
> ----------------------------------------------------------------
>
> Key: OFBIZ-9380
> URL: https://issues.apache.org/jira/browse/OFBIZ-9380
> Project: OFBiz
> Issue Type: Bug
> Affects Versions: Release Branch 14.12
> Reporter: Chuck Kosta
>
> {code}
> <@htmlTemplate.renderDateTimeField ... />
> {code}
> Works correctly in IE; but in firefox and chrome, it ignores the values when
> sent to an entity updating service call. The page gets refreshed with the
> original date.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
