ICEfaces
  1. ICEfaces
  2. ICE-11513

Pressing Enter in ace:textEntry populates the field with inField label

    Details

      Description

      When an ace:textEntry has an inField label, if you focus on the field the label is removed, as expected, but if you press the Enter key, the field is populated with the label text.

        Activity

        Hide
        Arturo Zambrano added a comment -

        r53349: prevent submit on enter on ace:textEntry with inField label when the field is empty, in order to avoid having the field populated with the inField label while it has focus (4.x trunk)
        r53350: committed fix to EE 3.3 maintenance branch.

        The issue was that when pressing enter on an empty ace:textEntry field with an inField label the DOMdiff detected a difference in the input field from being populated with the value to being empty, so it sent an update of the input field only. The field couldn't be submitted with the label in it as the value, though. It required to blur the field and focus again to be able to submit a user-entered value. On the 4.x trunk, things were more complicated as we also have the lazy loading behaviour, where we don't initialize the ace:textEntry component unti it is focused. There was another issue with it where the component was being reinitialized multiple times across dynamic updates, and the focus and blur listeners were being accomulated on the input field.

        Show
        Arturo Zambrano added a comment - r53349: prevent submit on enter on ace:textEntry with inField label when the field is empty, in order to avoid having the field populated with the inField label while it has focus (4.x trunk) r53350: committed fix to EE 3.3 maintenance branch. The issue was that when pressing enter on an empty ace:textEntry field with an inField label the DOMdiff detected a difference in the input field from being populated with the value to being empty, so it sent an update of the input field only. The field couldn't be submitted with the label in it as the value, though. It required to blur the field and focus again to be able to submit a user-entered value. On the 4.x trunk, things were more complicated as we also have the lazy loading behaviour, where we don't initialize the ace:textEntry component unti it is focused. There was another issue with it where the component was being reinitialized multiple times across dynamic updates, and the focus and blur listeners were being accomulated on the input field.
        Hide
        Arturo Zambrano added a comment -

        r53356, r53357: moved the previous fix to another point in the code path that will allow the fix to be applied when secret=true (EE 3.3 maintenance branch and customer P08 branch)

        Show
        Arturo Zambrano added a comment - r53356, r53357: moved the previous fix to another point in the code path that will allow the fix to be applied when secret=true (EE 3.3 maintenance branch and customer P08 branch)
        Hide
        Arturo Zambrano added a comment -

        r53362: Keep the fix at the two points in the code necessary for the secret and normal cases to work, while making sure each of those code blocks is only applied to one case (secret or normal) (3.3 EE maintenance branch).

        r53361: Committed fix to customer's branch

        Show
        Arturo Zambrano added a comment - r53362: Keep the fix at the two points in the code necessary for the secret and normal cases to work, while making sure each of those code blocks is only applied to one case (secret or normal) (3.3 EE maintenance branch). r53361: Committed fix to customer's branch

          People

          • Assignee:
            Arturo Zambrano
            Reporter:
            Arturo Zambrano
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: