#4024 closed (duplicate)
Setting required=True in newforms Fields does not result in an change in as_p/as_ul/as_table
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | Forms | Version: | dev |
| Severity: | Keywords: | html_ouput as_p as_ul as_table required | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | yes |
| Needs tests: | yes | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
While it's nice to be able to set "required=True" and have it validate that properly, there is no hint given to the ui about this. My primary concern in this case is the generated content from html_output and the as_* functions. What I propose is a css_classes list in html_output that can be appended to by other attributes that might be set in the future, and a classes label for string concatenation added to the normal_row definitions.
Attachments (1)
Change History (6)
by , 18 years ago
| Attachment: | forms.py.diff added |
|---|
comment:2 by , 18 years ago
| Needs documentation: | set |
|---|---|
| Needs tests: | set |
Whoops, didn't mean to change the status.
comment:3 by , 18 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
comment:4 by , 18 years ago
hmmm maybe I don't understand how trac works here, but that definitely did not set my ticket as a duplicate of a specified ticket.
comment:5 by , 18 years ago
duplicate of #3512
(setting the ticket that this is a dup of in the message body is really backwards, and doesn't allow for particularly nice backlinking...shame on trac devs)
adds the ability to attach css classes to fields in generated output