You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2007/08/15 22:21:32 UTC

[jira] Assigned: (WICKET-447) Password field gets reset on setResetPassword == false even after successful validation

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

Igor Vaynberg reassigned WICKET-447:
------------------------------------

    Assignee: Igor Vaynberg

> Password field gets reset on setResetPassword == false even after successful validation
> ---------------------------------------------------------------------------------------
>
>                 Key: WICKET-447
>                 URL: https://issues.apache.org/jira/browse/WICKET-447
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.2.5
>         Environment: WinXP + java 1.5 + wicket 1.2.5
>            Reporter: Peter Ertl
>            Assignee: Igor Vaynberg
>             Fix For: 1.3.0-beta3
>
>
> I guess I found an issue when implementing a 'change password' dialog with these input fields (for simplicity in this example the [confirm password] field has been omitted):
> CHANGE PASSWORD FORM
> {
>   input type="password" [ old password ], setResetPassword(false)
>   input type="password" [ new password ], setResetPassword(false)
>   submit "Change Password"
> }
> All PasswordTextField's are set to setResetPassword(false). So I expect the input to be kept in the form on each request/response roundtrip.
> When I type in the [old password] but leave [new password] empty validation of [new password] fails as it is a required field. However the input of [old password] is not remembered but discarded This is wrong as the input for [old password] is valid and validation errors only relate to [new password]. So the user is forced to again enter all fields until validation succeeds as a whole.
> I tried the same with TextField's instead of PasswordTextField's: In this case the value of [old password] is kept even on validation error of [new password].
> Can you confirm this is an issue, please?!

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