Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: EE-4.1.0.RC1
-
Fix Version/s: EE-4.1.0.GA, 4.2.BETA, 4.2
-
Component/s: ACE-Components
-
Labels:None
-
Environment:ICEfaces EE-4.1.0 r48727, Tomcat 8, IE 11, FF 43, Chrome 50.
Myfaces libs only
-
Assignee Priority:P2
Description
ace:clientValidateLength, clientValidateDecimal, clientValidatePattern and clientValidateValueRange all fail when used with an ace:autoCompleteEntry and myfaces libs. Not an issue with mojarra.
Failures include and may not be limited to:
- Rendering an extra ace:autoCompleteEntry component at the bottom of the page every time a validation message is invoked.
- Removing characters from the autoCompleteEntry after the validation message is removed.
- Displaying multiple lists of the selectItems in the autoCompleteEntry, and not displaying the correct selections in the list.
To reproduce use the autoCompleteEntry ace:clientValidator tests found at:
http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Nightly/autoCompleteEntry.
1.) Build the application with myfaces libs.
2.) Use any of the clientValidator demos except for clientValidateRequired.
3.) Type into an autoCompleteEntry to invoke a validation message, look at the bottom of the test page to see additional autoCompleteEntries rendered.
4.) Type into the autoCompleteEntry to satisfy the requirement. When the requirement is met you will lose all input except for the first letter.
Failures include and may not be limited to:
- Rendering an extra ace:autoCompleteEntry component at the bottom of the page every time a validation message is invoked.
- Removing characters from the autoCompleteEntry after the validation message is removed.
- Displaying multiple lists of the selectItems in the autoCompleteEntry, and not displaying the correct selections in the list.
To reproduce use the autoCompleteEntry ace:clientValidator tests found at:
http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Nightly/autoCompleteEntry.
1.) Build the application with myfaces libs.
2.) Use any of the clientValidator demos except for clientValidateRequired.
3.) Type into an autoCompleteEntry to invoke a validation message, look at the bottom of the test page to see additional autoCompleteEntries rendered.
4.) Type into the autoCompleteEntry to satisfy the requirement. When the requirement is met you will lose all input except for the first letter.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
The issue with IE 9 where input was removed when typing into an autoCompleteEntry with clientValidateRequired is resolved.
The IE 8 js popup error is resolved.
Show
Liana Munroe
added a comment - The issue with IE 9 where input was removed when typing into an autoCompleteEntry with clientValidateRequired is resolved.
The IE 8 js popup error is resolved.
ICEfaces EE-4.1.0.GA Jenkins build 2 - Verified fixes to date.
Show
Liana Munroe
added a comment - ICEfaces EE-4.1.0.GA Jenkins build 2 - Verified fixes to date.
Changed element cloning implementation in ice.singleSubmit function to make sure no script element is cloned and thus evaluated by IE9.
Show
Mircea Toma
added a comment - - edited Changed element cloning implementation in ice.singleSubmit function to make sure no script element is cloned and thus evaluated by IE9.
Verified remaining ie9 + myfaces issues resolved. ICEfaces 4 trunk r48917.
Show
Liana Munroe
added a comment - Verified remaining ie9 + myfaces issues resolved. ICEfaces 4 trunk r48917.
Verified ICEfaces EE-4.1.0.GA Jenkins build 4. myfaces libs, tomcat 8, IE 11, 9, 8, FF 43, Chrome 50.
Show
Liana Munroe
added a comment - Verified ICEfaces EE-4.1.0.GA Jenkins build 4. myfaces libs, tomcat 8, IE 11, 9, 8, FF 43, Chrome 50.
Autocomplete component is using single submit requests to acquire the list of choices. The single submit function is cloning the node that does the submit and puts into a separate form used for submission. When running with Mojarra the cleanup code for the cloned elements is ran right away while with Myfaces the code is executed in only after the updates are applied (see http://jira.icesoft.org/browse/ICE-7562?focusedCommentId=37621&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-37621 ) . Since the submit is blocked by the client validation the after update callbacks (including the cleanup callback for the cloned elements) are not executed, hence the duplicate element that sticks around.