#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):
Yes, this makes a lot of sense; the reason I suggested a special marker is
backwards-compatibility -- if code exists which relies on the value being
converted to string, and so expects that attr=True will manifest in HTML
as `attr="True"`, this may very well break it.
I still find it preferable to use a special marker -- but I guess
`NoValue` is a bad name.
--
Ticket URL: <https://code.djangoproject.com/ticket/20684#comment:8>
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.394f5765a8a8f672a0cf40aea560d46a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
