ICEfaces
  1. ICEfaces
  2. ICE-11047

ace:clientValidateRequired with ace:fileEntry message display issue.

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Minor Minor
          • Resolution: Fixed
          • Affects Version/s: 4.1.1
          • Fix Version/s: EE-4.1.0.GA, 4.2.BETA, 4.2
          • Component/s: ACE-Components
          • Labels:
            None
          • Environment:
            Tomcat 8, all browsers, ICEfaces 4 trunk r48822
          • Assignee Priority:
            P2

            Description

            ace:clientValidateRequired message changes from red to yellow upon a second failed validation. Please see attached images.
            1.PNG - When the clientValidateRequired has been triggered. Achieve this by pressing the Upload button before browsing for a file.
            2.PNG - Message shown after uploading a file.
            3.PNG - If you press the Upload button again without first browsing for a file the validation message is a yellow warning message instead of a red message.
            1. 1.PNG
              14 kB
            2. 2.PNG
              31 kB
            3. 3.PNG
              31 kB

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Ken Fyten added a comment -

              Seems likely to be a CSS issue?

              Show
              Ken Fyten added a comment - Seems likely to be a CSS issue?
              Hide
              Permalink
              Arturo Zambrano added a comment -

              r48842: fix to update error classes in the client side, if they have been modified in the server side

              What happened was that the message node was updated from the server side to use the highlight style classes, after successfully uploading a file, and the client validator code didn't verify that the error classes were still there when displaying a new error message.

              Show
              Arturo Zambrano added a comment - r48842: fix to update error classes in the client side, if they have been modified in the server side What happened was that the message node was updated from the server side to use the highlight style classes, after successfully uploading a file, and the client validator code didn't verify that the error classes were still there when displaying a new error message.
              Hide
              Permalink
              Liana Munroe added a comment -

              Verified ICEfaces 4 trunk r 48844. Tomcat 8, IE 11, 10, 9, FF 43, Chrome 50.

              Show
              Liana Munroe added a comment - Verified ICEfaces 4 trunk r 48844. Tomcat 8, IE 11, 10, 9, FF 43, Chrome 50.
              Hide
              Permalink
              Liana Munroe added a comment -

              Some ace:clientValidator demos in showcase have a console error when using submit. This started with IF4 trunk Jenkins build 1993 with a commit for ICE-11047. All browsers.

              FF: TypeError: node.childNodes[0].childNodes[0] is undefined
              http://localhost:8080/showcase/javax.faces.resource/coalesced.js.jsf?ln=ice.core&dgst=emp3ot line 13961 > eval
              Line 168

              Chrome: VM186:667 Uncaught TypeError: Cannot read property 'className' of undefined. Exception occurred when checking element requiredForm:textEntry1_input, check the 'required' method.

              The demos affected are:
              ace:clientValidateRequired > Overview
              ace:clientValidateLength > Minimum, Min/Max range

              Show
              Liana Munroe added a comment - Some ace:clientValidator demos in showcase have a console error when using submit. This started with IF4 trunk Jenkins build 1993 with a commit for ICE-11047 . All browsers. FF: TypeError: node.childNodes [0] .childNodes [0] is undefined http://localhost:8080/showcase/javax.faces.resource/coalesced.js.jsf?ln=ice.core&dgst=emp3ot line 13961 > eval Line 168 Chrome: VM186:667 Uncaught TypeError: Cannot read property 'className' of undefined. Exception occurred when checking element requiredForm:textEntry1_input, check the 'required' method. The demos affected are: ace:clientValidateRequired > Overview ace:clientValidateLength > Minimum, Min/Max range
              Hide
              Permalink
              Arturo Zambrano added a comment -

              r48924: fix to correctly obtain the icon node in ace:messages when updating its class name

              Show
              Arturo Zambrano added a comment - r48924: fix to correctly obtain the icon node in ace:messages when updating its class name
              Hide
              Permalink
              Liana Munroe added a comment -

              Verified ICEfaces 4 trunk r48924. Tomcat 8, IE 11, 10, 9, 8, FF 43, Chrome 50.

              Show
              Liana Munroe added a comment - Verified ICEfaces 4 trunk r48924. Tomcat 8, IE 11, 10, 9, 8, FF 43, Chrome 50.
              Hide
              Permalink
              Liana Munroe added a comment -

              Verified ICEfaces EE-4.1.0.GA Jenkins build 4. Tomcat 8, IE 11, FF 43, Chrome 50.

              Show
              Liana Munroe added a comment - Verified ICEfaces EE-4.1.0.GA Jenkins build 4. Tomcat 8, IE 11, FF 43, Chrome 50.

                People

                • Assignee:
                  Arturo Zambrano
                  Reporter:
                  Liana Munroe
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: