Opened 17 years ago
Closed 17 years ago
#4480 closed (duplicate)
booleanfield newforms marked as editable=false must be set to true by the end user
| Reported by: | rogerdpack | Owned by: | nobody |
|---|---|---|---|
| Component: | Forms | Version: | dev |
| Severity: | Keywords: | newforms, booleanfield | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
May not be a problem, as you can specify editable=false, but
class ResponseToEvaluationUserWhoCreatedComment(forms.Form):
mark_as_cleared = forms.BooleanField()
seems to (for me), with newforms, require the user to check the checkbox. We could rename it "must be checked" :)
Change History (5)
comment:1 by , 17 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:2 by , 17 years ago
| Resolution: | invalid |
|---|---|
| Status: | closed → reopened |
I just fell into the same trap, and I wondered what's the use of a boolean field that must be set? Would you accept a patch that changes the default to required=false for BooleanField and NullBooleanField?
comment:4 by , 17 years ago
| Component: | Uncategorized → django.newforms |
|---|---|
| Keywords: | newforms booleanfield added |
comment:5 by , 17 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | reopened → closed |
Note:
See TracTickets
for help on using tickets.
Yes, this is the way it works by design. Use
BooleanField(required=False)if you don't want to have to have it checked.