#20684: Support form element attributes with no value
------------------------------+------------------------------------
Reporter: sneethling@… | Owner: nobody
Type: New feature | Status: new
Component: Forms | Version: 1.5
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+------------------------------------
Comment (by shai):
Actually, I'd rather use some special marker rather than None -- most such
attributes are essentially boolean, and None -- which is False when
evaluated as a boolean -- would come to mark True, and this can be
confusing.
I'd introduce a new constant, and call it NoValue -- probably along the
lines of `class NoValue(object): pass`. Then you could write
{{{
widget=forms.TextInput(
attrs={
'required': NoValue
}))
}}}
And also have correct behavior on things like `if
widget.attrs['required']: ...`
--
Ticket URL: <https://code.djangoproject.com/ticket/20684#comment:3>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/080.be0ec7c10820cf980d8b220cc0af0792%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
