You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Nicolas Barrera <nb...@gmail.com> on 2010/11/09 15:33:53 UTC
PasswordField usage question
Hi,
I 'm trying to use PasswordField for a CRUD I 'm implementing...,
in the create page I 'm fine with PasswordField, as it shows ***** instead
of the user input and on the server-side I got the real user input.
but, in the Update page I came across that the PasswordField is being shown
blank...,
I 've read the Component reference and the javadoc and I didn't realized how
to setup a different default value for a PasswordField to show..,
I 'd like the PasswordField to show an arbitrary number of **** as the
default value for the update page...,
that way the user can think of that field as it got a value which he doesn't
know which and think of updating it.
obviously I don't want those arbitrary ***** to become the new value of the
password if the user don't modify it.
Hope someone can drop me a line...,
cheers
Nicolás.-
Re: PasswordField usage question
Posted by Richard Hill <ri...@su3analytics.com>.
How about this:
Old password: *****
New Password: <blank>
Confirm new password: <blank>
The old password field is a dummy, populated with some random string.
However I'd argue from a user perspective if the field is labelled "new
password" there shouldn't be any confusion, and that the "old" field
isn't really needed.
-----Original Message-----
From: Nicolas Barrera <nb...@gmail.com>
To: Tapestry users <us...@tapestry.apache.org>, rich@su3analytics.com
Subject: Re: PasswordField usage question
Date: Tue, 9 Nov 2010 12:31:57 -0300
Thanks Richard,
you 're right with that of the password confirmation field, and with
that of the simplest and safest...
perhaps I can have a "change password" checkbox in order to give the
user the right sensation...,
i think that viewing in the modification page the empty password field
gives the user the possibility of misunderstand and think that the
current password is blank or something..,
perhaps with some modification to the manner in which i present the
fields i could remove that misunderstanding sensation.
thanks, again...
anyone..., if anyone knows a simple way to do this is welcome :)
bye
Nicolás.-
On Tue, Nov 9, 2010 at 12:20 PM, Richard Hill <ri...@su3analytics.com>
wrote:
A possibility is to have the password field populated with a
string
known to you. If this is submitted, ignore updating the
password.
Although of course this breaks if the user happens to choose the
same
password.
You could also have some client side js to populate a hidden
form input
if the user types in a new password, but again a bit flaky as
what
happens if the user has js off or he accidently focuses on the
field or
something?
Another possibility might be have a *** image as a background to
the
field (is this even possible?) and have it switch off on user
focus.
As far as I'm aware there's nothing in the html spec that'll
render *'s
in a password field if it's empty. Although I'd be interested to
hear
otherwise.
To be honest, it's probably simplest and safest to leave it
blank. (You
might want to consider adding a confirm password field too to
make sure
the user hasn't typo'd and leaves himself locked out of the app)
R.
-----Original Message-----
From: Nicolas Barrera <nb...@gmail.com>
Reply-to: "Tapestry users" <us...@tapestry.apache.org>
To: Tapestry users <us...@tapestry.apache.org>
Subject: PasswordField usage question
Date: Tue, 9 Nov 2010 11:33:53 -0300
Hi,
I 'm trying to use PasswordField for a CRUD I 'm
implementing...,
in the create page I 'm fine with PasswordField, as it shows
***** instead
of the user input and on the server-side I got the real user
input.
but, in the Update page I came across that the PasswordField is
being shown
blank...,
I 've read the Component reference and the javadoc and I didn't
realized how
to setup a different default value for a PasswordField to
show..,
I 'd like the PasswordField to show an arbitrary number of ****
as the
default value for the update page...,
that way the user can think of that field as it got a value
which he doesn't
know which and think of updating it.
obviously I don't want those arbitrary ***** to become the new
value of the
password if the user don't modify it.
Hope someone can drop me a line...,
cheers
Nicolás.-
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: PasswordField usage question
Posted by Nicolas Barrera <nb...@gmail.com>.
Thanks Richard,
you 're right with that of the password confirmation field, and with that of
the simplest and safest...
perhaps I can have a "change password" checkbox in order to give the user
the right sensation...,
i think that viewing in the modification page the empty password field gives
the user the possibility of misunderstand and think that the current
password is blank or something..,
perhaps with some modification to the manner in which i present the fields i
could remove that misunderstanding sensation.
thanks, again...
anyone..., if anyone knows a simple way to do this is welcome :)
bye
Nicolás.-
On Tue, Nov 9, 2010 at 12:20 PM, Richard Hill <ri...@su3analytics.com> wrote:
>
> A possibility is to have the password field populated with a string
> known to you. If this is submitted, ignore updating the password.
> Although of course this breaks if the user happens to choose the same
> password.
>
> You could also have some client side js to populate a hidden form input
> if the user types in a new password, but again a bit flaky as what
> happens if the user has js off or he accidently focuses on the field or
> something?
>
> Another possibility might be have a *** image as a background to the
> field (is this even possible?) and have it switch off on user focus.
>
> As far as I'm aware there's nothing in the html spec that'll render *'s
> in a password field if it's empty. Although I'd be interested to hear
> otherwise.
>
> To be honest, it's probably simplest and safest to leave it blank. (You
> might want to consider adding a confirm password field too to make sure
> the user hasn't typo'd and leaves himself locked out of the app)
>
> R.
>
>
> -----Original Message-----
> From: Nicolas Barrera <nb...@gmail.com>
> Reply-to: "Tapestry users" <us...@tapestry.apache.org>
> To: Tapestry users <us...@tapestry.apache.org>
> Subject: PasswordField usage question
> Date: Tue, 9 Nov 2010 11:33:53 -0300
>
> Hi,
>
> I 'm trying to use PasswordField for a CRUD I 'm implementing...,
>
> in the create page I 'm fine with PasswordField, as it shows ***** instead
> of the user input and on the server-side I got the real user input.
>
>
> but, in the Update page I came across that the PasswordField is being shown
> blank...,
> I 've read the Component reference and the javadoc and I didn't realized
> how
> to setup a different default value for a PasswordField to show..,
>
> I 'd like the PasswordField to show an arbitrary number of **** as the
> default value for the update page...,
> that way the user can think of that field as it got a value which he
> doesn't
> know which and think of updating it.
>
> obviously I don't want those arbitrary ***** to become the new value of the
> password if the user don't modify it.
>
> Hope someone can drop me a line...,
>
> cheers
>
> Nicolás.-
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: PasswordField usage question
Posted by Richard Hill <ri...@su3analytics.com>.
A possibility is to have the password field populated with a string
known to you. If this is submitted, ignore updating the password.
Although of course this breaks if the user happens to choose the same
password.
You could also have some client side js to populate a hidden form input
if the user types in a new password, but again a bit flaky as what
happens if the user has js off or he accidently focuses on the field or
something?
Another possibility might be have a *** image as a background to the
field (is this even possible?) and have it switch off on user focus.
As far as I'm aware there's nothing in the html spec that'll render *'s
in a password field if it's empty. Although I'd be interested to hear
otherwise.
To be honest, it's probably simplest and safest to leave it blank. (You
might want to consider adding a confirm password field too to make sure
the user hasn't typo'd and leaves himself locked out of the app)
R.
-----Original Message-----
From: Nicolas Barrera <nb...@gmail.com>
Reply-to: "Tapestry users" <us...@tapestry.apache.org>
To: Tapestry users <us...@tapestry.apache.org>
Subject: PasswordField usage question
Date: Tue, 9 Nov 2010 11:33:53 -0300
Hi,
I 'm trying to use PasswordField for a CRUD I 'm implementing...,
in the create page I 'm fine with PasswordField, as it shows ***** instead
of the user input and on the server-side I got the real user input.
but, in the Update page I came across that the PasswordField is being shown
blank...,
I 've read the Component reference and the javadoc and I didn't realized how
to setup a different default value for a PasswordField to show..,
I 'd like the PasswordField to show an arbitrary number of **** as the
default value for the update page...,
that way the user can think of that field as it got a value which he doesn't
know which and think of updating it.
obviously I don't want those arbitrary ***** to become the new value of the
password if the user don't modify it.
Hope someone can drop me a line...,
cheers
Nicolás.-
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org