Opened 3 years ago
Last modified 3 years ago
#32905 closed New feature
Add `nonform` CSS class for non form errors in FormSets — at Version 3
| Reported by: | Ties Jan Hefting | Owned by: | Ties Jan Hefting |
|---|---|---|---|
| Component: | Forms | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
Forms add the nonfield CSS class for non field errors in ErrorList instances. This is documented in a section on rendering form error messages. Similarly, in FormSets I'd expect to see the nonform CSS class added for non form errors. This would allow a custom ErrorList to make a distinction in form field errors, non field errors (forms) and non form errors (FormSets) when rendering error messages. Therefore I'd suggest to add this nonform CSS class and document it for developers to use.
Change History (3)
comment:1 by , 3 years ago
| Owner: | changed from to |
|---|
comment:2 by , 3 years ago
| Easy pickings: | unset |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
| Type: | Cleanup/optimization → New feature |
Note:
See TracTickets
for help on using tickets.
Seems reasonable (similar to #11776).