Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Cannot Reproduce
-
Affects Version/s: 4.0
-
Fix Version/s: 4.1
-
Component/s: ACE-Components
-
Labels:None
-
Environment:ICEfaces 4 trunk, Tomcat
-
Assignee Priority:P1
-
Workaround Exists:Yes
-
Workaround Description:The least impactful workaround is probably to use a pattern without seconds (ie: "MM/dd/yyyy h:mm a"), since renderAsPopup and min/max date are pretty important.
Description
This specific combination of attributes makes the DateTimeEntry unclickable:
<ace:dateTimeEntry value="#{bean.ourDate}"
renderAsPopup="true"
mindate="#{controller.minDate}"
maxdate="#{controller.maxDate}"
showOn="both"
pattern="MM/dd/yyyy h:mm:ss a"/>
It works fine if we do:
renderAsPopup="false"
OR
no mindate or maxdate
OR
pattern="MM/dd/yyyy h:mm a"
So it seems to be something with the interaction between the popup, the min/max date, and the time entry for seconds.
<ace:dateTimeEntry value="#{bean.ourDate}"
renderAsPopup="true"
mindate="#{controller.minDate}"
maxdate="#{controller.maxDate}"
showOn="both"
pattern="MM/dd/yyyy h:mm:ss a"/>
It works fine if we do:
renderAsPopup="false"
OR
no mindate or maxdate
OR
pattern="MM/dd/yyyy h:mm a"
So it seems to be something with the interaction between the popup, the min/max date, and the time entry for seconds.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion