Hi,

It's true that the value is required to be in YYYY-MM-DD format, but in
modern browsers (which I think is what we claim to support now, right?) it
will show in the user's localised format. I checked this in Firefox,
Chrome, Edge, and they all look good to me - they come with both a date
picker, and allow you to enter the date in your local format. So I think
the time has come where this might be a beneficial change (for #21470).
However, Firefox is lacking a picker for <input type="datetime-local">
until the next version, though presumably that will be released before any
change here would make it in.

Probably the problem here is that if we make this the default, we will
break people's code who are not explicitly rendering their forms.

It also might be nice to use these in the admin and remove our own date
picker code, if it doesn't pose any problems.

I realise this isn't actually an answer to your initial question, though.

Cheers,
Tom

On Tue, 28 Sept 2021 at 11:16, Carlton Gibson <carlton.gib...@gmail.com>
wrote:

> Hi all.
>
> There's a PR to add examples using `<input type=date ...>` for
> `forms.DateInput`.
> https://github.com/django/django/pull/14905
>
> Support for HTML5 input types was added a long time back now in #16630
> <https://code.djangoproject.com/ticket/16630>.
> Back then there were various issues with localisation when **not** using
> type=text.
> See https://code.djangoproject.com/ticket/16630#comment:11 and following
> discussion.
> The original mailing list thread is here
> <https://groups.google.com/g/django-developers/c/DENf3jq1F_w/m/LJvTMpbwoVQJ>
> .
>
> The goal is to say something succinct but accurate that covers both sides
> of "Why the default is type=text" and "What you need to consider using
> type=date".
>
> Can we solicit some input (🥁) on what issues folks hit? — specifically
> for DateInput the concern was the required date format (I think).
>
> It may well be that things have changed since 2012? (If so we might
> revisit #21470 <https://code.djangoproject.com/ticket/21470>.)
>
> Thanks.
> Carlton
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/16d05604-4068-4423-9ac4-f8f520d44a42n%40googlegroups.com
> <https://groups.google.com/d/msgid/django-developers/16d05604-4068-4423-9ac4-f8f520d44a42n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAHoz%3DMYCeFm-CHosr6TE%2BmuO3%2BgY-B97KmskozNX5rfYi4GMkA%40mail.gmail.com.

Reply via email to