I with banking software. For me things are bit different. Inline error although is a god idea but most of the forms being large and having constraint of showing maximum in one page kinda rules it out. Combine with it numerous validation error which might occur, developers shy away from providing specific error messages and prefer throwing generic and even in some cases technical error messages.
Any proven method how to show error in such situation? Of course simplifying the form itself will solve lot of problem, but yet we are left with lot of fields and more the field more the chance of error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=31032 ________________________________________________________________ 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
