#20684: Support form element attributes with no value
------------------------------+------------------------------------
Reporter: sneethling@… | Owner: nobody
Type: New feature | Status: new
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 1 | UI/UX: 0
------------------------------+------------------------------------
Comment (by shai):
Constant string: `Starting from Django 1.8, boolean values to widget
attributes will determine if the attribute appears (with no value). To
preserve current behavior, use string values explicitly`.
Or, taking the approach of @jcd -- why not go all the way?
When value is True: `Starting from Django 1.8, widget attribute
%(attr_name)s=True will be rendered as '%(attr_name)s'. To preserve
current behavior, use the string 'True' instead of the boolean True.`
When value is False: `Starting from Django 1.8, widget attribute
%(attr_name)s=False will be not be rendered. To preserve current behavior,
use the string 'False' instead of the boolean False.`
--
Ticket URL: <https://code.djangoproject.com/ticket/20684#comment:32>
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.17efa666906eeadcd8c8f66bbc30dafa%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
