+1 on telling the user that the e-mail address will actually be used for
something when we have account activation turned on.
Brian Moseley wrote:
we also need to improve the clarity of our error reporting on the
signup page. rather than sticking some random poorly worded message up
at the top of the form where it's not immediately noticeable, we
should put clear, detailed feedback right at the problem where the
error has occurred.
In the signup page at least, there are very specific errors that show in
red, directly over the form input, explaining exactly what the problem
is -- for example, "This field requires a minimum length. (3)," "This
field must match Password field," or "This field must be a valid e-mail
address."
What random, poorly worded message are you referring to? The min. length
prompt is oddly worded, but I don't think it's particuarly unclear.
We have an open bug (7907) for improving error messages in the UI in
general. It's currently classified as an enhancement, but it could
potentially be bumped up in priority.
we should also state our expectations for syntax,
length etc next to every field in the form when it's first rendered.
Adding the requirements such as minimum length or 'must be valid e-mail
address' up-front is an excellent idea.
M.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
