Opened 15 years ago
Closed 15 years ago
#10442 closed (wontfix)
Better support for readonly Form fields
| Reported by: | Luc Saffre | Owned by: | Luc Saffre |
|---|---|---|---|
| Component: | Forms | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I saw ticket #3990 , but IMHO, if a ModelForm has an explicit {{{fields}} list,
and if some of these fields are not editable, then they should be rendered as readonly widgets.
That's the least surprising behaviour. Currently they are just ignored.
I am trying to write a patch, but I'm new to Django.
Note:
See TracTickets
for help on using tickets.
This looks like a direct dupe of #3990 that you've already found. Since the first step in fixing that requires writing a field-like class that provides static rendering (not a readonly form-field), we should keep this all together in one ticket. So closing as a dupe, since it's very difficult to track something split over multiple tickets doing the same thing.