[EMAIL PROTECTED] wrote:
But in fact it does not look user intuitive.
I concur with this statement. I've got a form with about 10 fields and when there are multiple errors for adjacent fields, it's very hard to tell if the error is for the field above or below.
The problem is visual. I do not like to present end users so ugly looking errors. As temp. solution I have patched as_table() output, so it takes optional argument: errors_on_separate_row
-0 My vote would be to change as_table() to make it more pleasing to the eye rather than introduce a parameter. The errors on a seperate row is pretty unusable and we should not allow the creation of such forms in Django :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
