[jira] Resolved: (WICKET-322) Odd behvavior with PasswordTextField evaluation

["Igor Vaynberg (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg resolved WICKET-322.
----------------------------------

    Resolution: Fixed

i removed the encryption as it didnt always work and cause weird problems, so this should now also be fixed

> Odd behvavior with PasswordTextField evaluation
> -----------------------------------------------
>
>                 Key: WICKET-322
>                 URL: https://issues.apache.org/jira/browse/WICKET-322
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.2.5, 1.2.6
>         Environment: Jetty 6, JDK 1.5
>            Reporter: Rüdiger Schulz
>             Fix For: 1.3.0-beta3
>
>         Attachments: PasswordTextField.java
>
>
> Given a sign-up form with a password field like this:
> PasswordTextField passwordField = new PasswordTextField("password");
> passwordField.setRequired(true);
> passwordField.add(StringValidator.lengthBetween(5, 32));
> I observe a rather odd behavior:
> 1) enter 5 characters, submit. Other fields in the form have errors, so the form is redisplayed.
> 2) delete a character, submit. Error is displayed, but the value of the field is what I entered in step 1.
> 3) result: submitting again just works, which shouldn't be the case with any form displaying an error.
> This is especially irritating if you do the form validation via Ajax after onblur, so it would be nice if this could be changed somehow.
> See also here:
> http://www.nabble.com/PasswordTextField.setResetPassword-tf1399513.html#a3764720

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.