#16630: Support for HTML5 input types
-----------------------------+------------------------------------
Reporter: jonash | Owner: nobody
Type: New feature | Status: new
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: html5 | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
Changes (by carljm):
* stage: Design decision needed => Accepted
Comment:
IMO this is a change we simply need to make at some point in order to stay
up to date, and waiting won't make the (minor) CSS/JS backwards-
incompatibilities any less incompatible. We could do something more
complex like a settings-flag to enable the change, but I really don't
think the compatibility issues are worth that; we've never made any
backwards-compatibility promises regarding form HTML output.
#15667 is not really relevant, as it's not clear if that can even happen,
due to performance issues with the template engine. And in any case, this
doesn't prevent that. So I think we should just go ahead and do this.
Though we definitely do need to note the output changes in the "backwards
incompatibilities" section of the release notes, so the patch is still
lacking that.
--
Ticket URL: <https://code.djangoproject.com/ticket/16630#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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
