#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
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* type: Uncategorized => Cleanup/optimization
* component: Forms => Documentation
* stage: Unreviewed => Accepted
Comment:
Hi Thibaud.
Initially let's accept this as a Documentation issue. Certainly we can do
that right? 😀
**Very happy** to consider specific changes that you come up with here
too!
Without some idea of what we might do though, it's a bit `needsinfo` —
maybe targeted changes for single fields to begin...?
A proof-of-concept here would help push it forward.
Thanks! 👍
--
Ticket URL: <https://code.djangoproject.com/ticket/32340#comment:1>
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.1583f0a2a8b9a001c6c701b432e39257%40djangoproject.com.
