#32340: Usability issues with Django form fields expecting specific patterns
-------------------------------------+-------------------------------------
Reporter: Thibaud Colas | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: accessibility, | Triage Stage: Accepted
usability, forms |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
Comment (by Thibaud Colas):
Thank you, I think I’ll start with getting more familiar with the
documentation so I can figure out where best to address this. And as I do
I’ll likely have to come up with code snippets that might inform further
changes.
I think it would also be good to get feedback from others here – on the
specific issues outlined here, and perhaps also more generally on how much
it’s Django’s role to make sure it’s not too easy to misuse.
--
Ticket URL: <https://code.djangoproject.com/ticket/32340#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.3f8e019a24f77cf15178c48a84c7d0eb%40djangoproject.com.
