I have seen cases where a space is allotted for where an error message
will go if it occurs. Designed well, users with no error never notice
that the space is there, it just integrates into the design. (I've
also seen this done poorly, of course where there's a big obvious
blank space.)
-- Jim
Via my iPhone
On Nov 6, 2008, at 7:53 AM, Rachel <[EMAIL PROTECTED]> wrote:
I'm working on an Ajax app that will have edit-in-place forms
(a.k.a. inline
editing). Page has read-only data; parts of the data are editable.
User
chooses to edit a part; that part turns into an editable form. When
user
saves changes, the form converts back to read-only data (this happens
without a page reload).
The fields in the forms are required. So if user leaves any blank,
they need
to be challenged, and we need to let them know which fields are in
question.
What's the best way to handle this?
We are reluctant to show an error message right above the form,
because it
will push the form & other content on the page downward, creating a
visual
"jumping" effect. (unless we overlay the error message over top of
other
content on the page)
What are best practices for this? Good examples?
Thanks,
Rachel
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [EMAIL PROTECTED]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [EMAIL PROTECTED]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help
