Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 4.1
-
Fix Version/s: 4.1.1
-
Component/s: ACE-Components
-
Labels:None
-
Environment:Liferay/Portlet but likely a webapp problem as well
-
Assignee Priority:P1
Description
Steps to Reproduce:
1. Start Liferay Portal 7.0-B7
2. Deploy the attached icefaces4-portlet-4.0.0-SNAPSHOT.war artifact to $LIFERAY_HOME/deploy
3. Add the ICEfaces4 portlet to a new portal page
4. Reload the page
5. When the applicant form is rendered, click in the "Date of Birth" field in order to cause the calendar to popup.
6. Enter an invalid date via the keyboard and press TAB: 02/30/2016
7. Observe that the field turns red in the browser and in the server log, that only the RESTORE_VIEW, APPLY_REQUEST_VALUES, PROCESS_VALIDATIONS, and RENDER_RESPONSE phases were executed. In other words, the UPDATE_MODEL_VALUES and INVOKE_APPLICATION phases are skipped since the date of birth value is invalid.
8. Using the mouse, click in the Date of Birth field in order to popup the calendar and then click on any date in the calendar so that the value is valid.
9. Observe in the server log that all phases of the JSF lifecycle were executed.
10. Click in the "Date of Birth" field and enter an invalid date via the keyboard and press TAB: 02/30/2016
If the bug is fixed, then the behavior of step#7 should be observed, meaning that the UPDATE_MODEL_VALUES and INVOKE_APPLICATION phases are skipped.
If the bug still exists, then an XHR will not be submitted at all and the field will not turn red.
1. Start Liferay Portal 7.0-B7
2. Deploy the attached icefaces4-portlet-4.0.0-SNAPSHOT.war artifact to $LIFERAY_HOME/deploy
3. Add the ICEfaces4 portlet to a new portal page
4. Reload the page
5. When the applicant form is rendered, click in the "Date of Birth" field in order to cause the calendar to popup.
6. Enter an invalid date via the keyboard and press TAB: 02/30/2016
7. Observe that the field turns red in the browser and in the server log, that only the RESTORE_VIEW, APPLY_REQUEST_VALUES, PROCESS_VALIDATIONS, and RENDER_RESPONSE phases were executed. In other words, the UPDATE_MODEL_VALUES and INVOKE_APPLICATION phases are skipped since the date of birth value is invalid.
8. Using the mouse, click in the Date of Birth field in order to popup the calendar and then click on any date in the calendar so that the value is valid.
9. Observe in the server log that all phases of the JSF lifecycle were executed.
10. Click in the "Date of Birth" field and enter an invalid date via the keyboard and press TAB: 02/30/2016
If the bug is fixed, then the behavior of step#7 should be observed, meaning that the UPDATE_MODEL_VALUES and INVOKE_APPLICATION phases are skipped.
If the bug still exists, then an XHR will not be submitted at all and the field will not turn red.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Neil Griffin
created issue -
Neil Griffin
made changes -
Field | Original Value | New Value |
---|---|---|
Attachment | icefaces4-portlet-4.0.0-SNAPSHOT.war [ 22084 ] |
Ken Fyten
made changes -
Assignee | Arturo Zambrano [ artzambrano ] | |
Fix Version/s | 4.1.1 [ 12972 ] | |
Assignee Priority | P1 [ 10010 ] |
Arturo Zambrano
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Summary | ace:dateTimeEntry does not submit invalid dates via XHR after a valid date has been selected | ace:dateTimeEntry onchange event not re-registered when component is re-initialized |
Carmen Cristurean
made changes -
Attachment | icefaces4-portlet-4.1.1.war [ 22093 ] |
Carmen Cristurean
made changes -
Attachment | icefaces4-portlet-4.1.1.war [ 22093 ] |
Carmen Cristurean
made changes -
Attachment | icefaces4-portlet-4.1.1.war [ 22094 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |