ICEfaces
  1. ICEfaces
  2. ICE-10978

ace:textEntry - Does not submit onblur with secret="true"

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: EE-3.3.0.GA_P03
          • Fix Version/s: EE-3.3.0.GA_P04
          • Component/s: ACE-Components
          • Labels:
            None
          • Environment:
            All

            Description

            When an ace:textEntry has secret="true", it does not submit onblur event, which in turn prevents the required validation from firing. It does submit when the enter key is pressed in the textEntry input field.

            This is not an issue with ICEfaces 4.x.

              Issue Links

              blocks

              Improvement - An improvement or enhancement to an existing feature or task. ICE-11014 ace:textEntry, replace input element when setting it to type="password"

              • Major - Major loss of function.
              • Closed

                Activity

                Ascending order - Click to sort in descending order
                Arran Mccullough created issue -
                Hide
                Permalink
                Arran Mccullough added a comment -

                Attached test case that shows this issue.

                Steps:

                • Load welcomeICEfaces.jsf
                • Set focus into the first input field.
                • Tab out or move the focus to the next field. The required validation should fire but does not.
                • Doing the same action on the second input field, the required validation is fired correctly on blur.
                Show
                Arran Mccullough added a comment - Attached test case that shows this issue. Steps: Load welcomeICEfaces.jsf Set focus into the first input field. Tab out or move the focus to the next field. The required validation should fire but does not. Doing the same action on the second input field, the required validation is fired correctly on blur.
                Arran Mccullough made changes -
                Field Original Value New Value
                Attachment Case13715Example.war [ 22099 ]
                Attachment Case13715Example.zip [ 22100 ]
                Ken Fyten made changes -
                Assignee Arturo Zambrano [ artzambrano ]
                Fix Version/s EE-4.1.0.GA [ 12171 ]
                Fix Version/s EE-3.3.0.GA_P04 [ 12270 ]
                Assignee Priority P2 [ 10011 ]
                Ken Fyten made changes -
                Fix Version/s EE-4.1.0.GA [ 12171 ]
                Hide
                Permalink
                Arturo Zambrano added a comment -

                r48661: wrapped lines where the type attribute is dynamically changed to 'password' inside try-catch clauses to avoid javascript errors

                In order to support inField labels on secret text fields, it is necessary to dynamically change the 'type' attribute of the 'input' element to/from 'password'. It seems like dynamically changing the type attribute of an input element is not permitted, so an error is thrown, which aborts the init function, before the behaviours are applied to the text field. As per ICE-10374, this was fixed on the 4.0 trunk, and this error was only seen on IE8. It seems like recent browser updates also started to throw this error. This is fixed with try-catch clauses. Even though, this change is supposedly not permitted, it can still be done, and no errors are thrown with these try-catch clauses.

                Show
                Arturo Zambrano added a comment - r48661: wrapped lines where the type attribute is dynamically changed to 'password' inside try-catch clauses to avoid javascript errors In order to support inField labels on secret text fields, it is necessary to dynamically change the 'type' attribute of the 'input' element to/from 'password'. It seems like dynamically changing the type attribute of an input element is not permitted, so an error is thrown, which aborts the init function, before the behaviours are applied to the text field. As per ICE-10374, this was fixed on the 4.0 trunk, and this error was only seen on IE8. It seems like recent browser updates also started to throw this error. This is fixed with try-catch clauses. Even though, this change is supposedly not permitted, it can still be done, and no errors are thrown with these try-catch clauses.
                Arturo Zambrano made changes -
                Status Open [ 1 ] Resolved [ 5 ]
                Resolution Fixed [ 1 ]
                Arturo Zambrano made changes -
                Resolution Fixed [ 1 ]
                Status Resolved [ 5 ] Reopened [ 4 ]
                Arturo Zambrano made changes -
                Link This issue blocks ICE-11014 [ ICE-11014 ]
                Hide
                Permalink
                Arturo Zambrano added a comment -

                Resolving issue. The fix above was improved as described in ICE-11014.

                Show
                Arturo Zambrano added a comment - Resolving issue. The fix above was improved as described in ICE-11014 .
                Arturo Zambrano made changes -
                Status Reopened [ 4 ] Resolved [ 5 ]
                Resolution Fixed [ 1 ]
                Ken Fyten made changes -
                Status Resolved [ 5 ] Closed [ 6 ]

                  People

                  • Assignee:
                    Arturo Zambrano
                    Reporter:
                    Arran Mccullough
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    2 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: