#32820: Fields’ errors should be programmatically associated with fields.
-------------------------------------+-------------------------------------
Reporter: Thibaud Colas | Owner: nobody
Type: Bug | Status: new
Component: Forms | Version: 3.2
Severity: Normal | Resolution:
Keywords: accessibility, ui, | Triage Stage: Accepted
forms |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tom Carrick):
Kiran, assign yourself the ticket if you want to take it. If you need
help, I would first read
https://docs.djangoproject.com/en/3.2/internals/contributing/ and try to
get the tests passing at least.
You would probably need to find where the HTML for these forms are
generated. I think
https://github.com/django/django/tree/main/django/forms/templates/django/forms/widgets
might be a good place to start. Then find out the best way to tell if the
field is invalid and the best place to add the attribute.
If you get stuck, you could try posting on the forum or the django-
developers mailing list.
--
Ticket URL: <https://code.djangoproject.com/ticket/32820#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.01d60a878e62b28d9a88496fd5361cc8%40djangoproject.com.
