Details
- 
        Type:
 Bug
            
         - 
        Status: Closed
 - 
            Priority:
 Major
                
             - 
            Resolution: Fixed
 - 
            Affects Version/s: EE-4.1.0.GA
 - 
            Component/s: ACE-Components
 - 
            Labels:None
 - 
            Environment:Tomcat 7/8, FF 47, IE 11, Chrome 52.
 
- 
                        Assignee Priority:P2
 - 
                        Affects:Compatibility/Configuration
 
Description
                    Issue found when using multiple ace:autoCompleteEntry components with ace:clientValidateRequired in one form.
Using this configuration the ace:autoCompleteEntry does not behave as expected.
Scenario:
A form has 3 ace:autoCompleteEntry components, each use an ace:clientValidateRequired within.
After typing only one character into the first ace:autoCompleteEntry the validation messages for the 2nd and third autoCompleteEntry are immediately rendered.
This can be reproduced with the /ICE-10883.jsf test app found at
http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Nightly/autoCompleteEntry
Using this configuration the ace:autoCompleteEntry does not behave as expected.
Scenario:
A form has 3 ace:autoCompleteEntry components, each use an ace:clientValidateRequired within.
After typing only one character into the first ace:autoCompleteEntry the validation messages for the 2nd and third autoCompleteEntry are immediately rendered.
This can be reproduced with the /
http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Nightly/autoCompleteEntry
Run validation only when the entire form is executed. Cleanup validation messages for elements that where changed after last submit and now pass validation.