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
The initial issue came up in the trunk auction monitor (icefaces/samples/ace/auction) on the Add Auction page (post-tab.xhtml). I'll update, change the attributes, and check it again to verify there.
Show
Carlo Guglielmin
added a comment - The initial issue came up in the trunk auction monitor (icefaces/samples/ace/auction) on the Add Auction page (post-tab.xhtml). I'll update, change the attributes, and check it again to verify there.
I can't reproduce it anymore, maybe it got fixed by another change in trunk. I'll mark invalid, thanks.
Show
Carlo Guglielmin
added a comment - I can't reproduce it anymore, maybe it got fixed by another change in trunk. I'll mark invalid, thanks.
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:
<ace:dateTimeEntry id="cal" value="#{dateMinMax.selectedDate}" renderAsPopup="true" mindate="#{dateMinMax.minDate}" maxdate="#{dateMinMax.maxDate}" showOn="both" pattern="MM/dd/yyyy h:mm:ss a"/>I'm attaching the source file as well.
If there's another way to reproduce it, please let me know.