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
Carlo Guglielmin
created issue -
Ken Fyten
made changes -
Field | Original Value | New Value |
---|---|---|
Affects Version/s | 4.0 [ 11382 ] | |
Affects Version/s | 4.1 [ 11375 ] |
Ken Fyten
made changes -
Fix Version/s | 4.1 [ 11375 ] |
Carlo Guglielmin
made changes -
Workaround Description | The last 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. | 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. |
Workaround Exists | Yes [ 10007 ] |
Ken Fyten
made changes -
Assignee | Arturo Zambrano [ artzambrano ] | |
Assignee Priority | P1 [ 10010 ] |
Arturo Zambrano
made changes -
Attachment | dateminmax.xhtml [ 19887 ] |
Arturo Zambrano
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Cannot Reproduce [ 5 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
I haven't been able to reproduce this issue. I modified the last ace:dateTimeEntry component in the dateminmax.xhtml page on the showcase to use those exact attributes in the description, but the component is fully functional. This is how the markup for the component looks like after modifying it:
I'm attaching the source file as well.
If there's another way to reproduce it, please let me know.