ICEfaces
  1. ICEfaces
  2. ICE-11035

ace:autoCompleteEntry with ace:clientValidators fail with myfaces libs

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major 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.

        Activity

        Liana Munroe created issue -
        Liana Munroe made changes -
        Field Original Value New Value
        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.
        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.
        Ken Fyten made changes -
        Assignee Mircea Toma [ mircea.toma ]
        Fix Version/s EE-4.1.0.GA [ 12171 ]
        Assignee Priority P2 [ 10011 ]
        Mircea Toma made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Ken Fyten made changes -
        Security Private [ 10001 ]
        Ken Fyten made changes -
        Resolution Fixed [ 1 ]
        Status Resolved [ 5 ] Reopened [ 4 ]
        Mircea Toma made changes -
        Status Reopened [ 4 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Liana Munroe made changes -
        Resolution Fixed [ 1 ]
        Status Resolved [ 5 ] Reopened [ 4 ]
        Mircea Toma made changes -
        Status Reopened [ 4 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Liana Munroe made changes -
        Resolution Fixed [ 1 ]
        Status Resolved [ 5 ] Reopened [ 4 ]
        Mircea Toma made changes -
        Status Reopened [ 4 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Ken Fyten made changes -
        Fix Version/s 4.2.BETA [ 13091 ]
        Fix Version/s 4.2 [ 12870 ]
        Ken Fyten made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            Mircea Toma
            Reporter:
            Liana Munroe
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: