You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Rüdiger Schulz (JIRA)" <ji...@apache.org> on 2007/06/02 19:36:15 UTC

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

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

Rüdiger Schulz updated WICKET-322:
----------------------------------

        Fix Version/s: 1.3.0-beta2
                       1.2.7
    Affects Version/s: 1.3.0-beta2
                       1.2.6

I switched to Wicket 1.3.0 from trunk, and I still think that getInput() should be used. The following works very well for me:

	protected final void onComponentTag(final ComponentTag tag)
	{
		super.onComponentTag(tag);
//		tag.put("value", getResetPassword() ? "" : getModelObjectAsString());
		tag.put("value", getResetPassword() ? "" : getInput());
	}


> 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, 1.3.0-beta2
>         Environment: Jetty 6, JDK 1.5
>            Reporter: Rüdiger Schulz
>             Fix For: 1.2.7, 1.3.0-beta2
>
>         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.