#35314: Django 5 breaks value of Date field rendering correctly in template
---------------------------+--------------------------------------
Reporter: Michael | Owner: nobody
Type: Bug | Status: closed
Component: Forms | Version: 5.0
Severity: Normal | Resolution: duplicate
Keywords: form date | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------+--------------------------------------
Comment (by Michael):
Replying to [comment:8 Natalia Bidart]:
> Replying to [comment:7 Michael]:
> > Seems a bit counter intuitive to have a broken date input format by
default.
>
> This feels a bit of a over statement, since Django does not support
(yet) `type="date"` input (see #21470). Were you able to read the related
issues I linked? This conversation is also quite relevant:
https://groups.google.com/g/django-developers/c/wp-pnzcB25o/m/D5gEOzPIAQAJ
Sorry, I should have toned it down and said the value being passed into
the date widgets is what doesn't work. The pattern that Django forms has
is quite a close relationship with HTML widgets. It's arguabley unexpected
the way that the `DateInput` is not an HTML `<input type="date">`. Thank
you for linking those conversations, sorry by the time I had answered the
question I forgot there were linked issues (kids handing off
arms/legs/calling for dinner time) and I lost track. Will checkout the
issues thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/35314#comment:9>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018e5350277a-7ddcfb11-c645-45ef-8ff1-584dbcbc8fff-000000%40eu-central-1.amazonses.com.
