Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: EE-3.3.0.GA_P02
-
Fix Version/s: EE-3.3.0.GA_P03
-
Component/s: ACE-Components, Sample Apps
-
Labels:None
-
Environment:3.3 P03 tag revision 44770, 3.3 maintenance branch rev. 44768 / MyFaces JSF specific
Browsers: all
Application: showcase
-
Assignee Priority:P2
Description
autoCompletEntry > Indicator Text
If required=true, after a validation error message is displayed, typing a letter in the component fails to display a list of possible options.
Steps:
- on the autoCompleteEntry - Indicator Text page, make sure the "Required" checkbox is selected.
- click inside the autoCompleteEntry, then without typing anything click outside the component -> a validation error message is rendered on page.
- type a letter in the autocompleteEntry -> the letter disappears, and there is no list of options displayed. Also, the validation error message is not removed until user clicks outside the demo panel.
This is also an issue with the 3.3 P02 libraries /MyFaces JSF only.
Not an issue on IF4 trunk /MyFaces or Mojarra JSF.
If required=true, after a validation error message is displayed, typing a letter in the component fails to display a list of possible options.
Steps:
- on the autoCompleteEntry - Indicator Text page, make sure the "Required" checkbox is selected.
- click inside the autoCompleteEntry, then without typing anything click outside the component -> a validation error message is rendered on page.
- type a letter in the autocompleteEntry -> the letter disappears, and there is no list of options displayed. Also, the validation error message is not removed until user clicks outside the demo panel.
This is also an issue with the 3.3 P02 libraries /MyFaces JSF only.
Not an issue on IF4 trunk /MyFaces or Mojarra JSF.
Committed fix to the 3.3 EE maintenance branch at revision 44779 and to the P03 tag at revision 44778.
This issue is the same one reported in ICE-10192, which just wasn't targeted for 3.3. So, ICE-10192 was backported to 3.3 to fix this issue. Basically, the fix consists in always setting the submitted value at any kind of request for the autocomplete component, so that validation runs against that submitted value and not the stored one. Another fix was also committed to solve a side effect of that change.