Re: [Django] #34853: Accept-Language Header takes precedence over cookie for format localization
Django
-------------------------------------+-------------------------------------
Reporter: blue-hexagon | Owner: nobody
Type: Bug | Status: new
Component: | Version: dev
Internationalization |
Severity: Normal | Resolution:
Keywords: l10n format | Triage Stage: Accepted
localization |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
Comment (by Natalia Bidart):
Replying to [comment:11 Claude Paroz]:
> Is the behavior the same if you remove `localized_fields`?
I can confirm the behavior is the same. I have completely commented out
the `localized_fields` definition in the `BookForm` and the date fields
are still showing in the language requested by my browser (es) and not in
the language defined by the language cookie (en).
--
Ticket URL: <https://code.djangoproject.com/ticket/34853#comment:13>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------------+-------------------------------------
Reporter: blue-hexagon | Owner: nobody
Component: | Version: dev
Internationalization |
Severity: Normal | Resolution: invalid
Keywords: l10n format | Triage Stage: Accepted
localization |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
* status: new => closed
* resolution: => invalid
Comment:
I had a look at your issue. This is an issue with the `<input
type="date">` widgets. And this is exactly why Django doesn't use
`type="date"` by default. With those inputs, browsers are forcing their
content to the format of the current active browser locale, whatever the
language of the page language. So Django cannot do anything to change
that.
Read the last comment of #34660 and the tickets/discussion it references.
--
Ticket URL: <https://code.djangoproject.com/ticket/34853#comment:14>
Django
-------------------------------------+-------------------------------------
Reporter: blue-hexagon | Owner: nobody
Type: Bug | Status: closed
Component: | Version: dev
Internationalization |
Severity: Normal | Resolution: invalid
Keywords: l10n format | Triage Stage: Accepted
localization |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
Comment (by Natalia Bidart):
Replying to [comment:14 Claude Paroz]:
> I had a look at your issue. This is an issue with the `<input
type="date">` widgets. And this is exactly why Django doesn't use
`type="date"` by default. With those inputs, browsers are forcing their
content to the format of the current active browser locale, whatever the
language of the page language. So Django cannot do anything to change
that.
>
> Read the last comment of #34660 and the tickets/discussion it
references.
Thank you Claude, I missed the override for the widget's type attr. TIL
many things regarding this topic!
--
Ticket URL: <https://code.djangoproject.com/ticket/34853#comment:15>
Django
-------------------------------------+-------------------------------------
Reporter: blue-hexagon | Owner: nobody
Type: Bug | Status: closed
Component: | Version: dev
Internationalization |
Severity: Normal | Resolution: invalid
Keywords: l10n format | Triage Stage:
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
* stage: Accepted => Unreviewed
--
Ticket URL: <https://code.djangoproject.com/ticket/34853#comment:16>
Django
-------------------------------------+-------------------------------------
Reporter: blue-hexagon | Owner: nobody
Type: Bug | Status: closed
Component: | Version: dev
Internationalization |
Severity: Normal | Resolution: invalid
Keywords: l10n format | Triage Stage:
localization | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
Replying to [comment:14 Claude Paroz]:
> I had a look at your issue. This is an issue with the `<input
type="date">` widgets. And this is exactly why Django doesn't use
`type="date"` by default. With those inputs, browsers are forcing their
content to the format of the current active browser locale, whatever the
language of the page language. So Django cannot do anything to change
that.
>
> Read the last comment of #34660 and the tickets/discussion it
references.
saying is Django does not provide a `<input type="date">` because the
`value` should be set according to the active browser's locale, which
Django doesn't know server side? If that is what you are saying, I
disagree, it is always in the format "YYYY-MM-DD", see:
Date input on MDN: https://developer.mozilla.org/en-
US/docs/Web/HTML/Element/input/date
Date Time Format on MDN: https://developer.mozilla.org/en-
US/docs/Web/HTML/Date_and_time_formats#date_strings
> HTML uses a variation of the ISO 8601 standard for its date and time
strings.
It would be very simple to have Django render date value's server side
such that it works correctly with `<input type="date">`, it just has to do
less ....like in Django 4, instead of forcing the default language's
DATE_INPUT_FORMAT to the settings language.
I opened an issue about this recently:
https://code.djangoproject.com/ticket/35314?replyto=8#comment
--
Ticket URL: <https://code.djangoproject.com/ticket/34853#comment:17>
Django
-------------------------------------+-------------------------------------
Reporter: blue-hexagon | Owner: nobody
Type: Bug | Status: closed
Component: | Version: dev
Internationalization |
Severity: Normal | Resolution: invalid
Keywords: l10n format | Triage Stage:
localization | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
No, if you read the various related tickets and discussions, you'll see
that the problem is that browsers are very diverse in the manner they
render `<input type="date"> fields. At least it was an issue in the past
years (Safari was a typical example). I guess that at some point, we might
reconsider this and reevaluate if all browsers render it without usability
issues nowadays, and if it's the case we should then implement it in
Django.
Please open a discussion on the Django forum if you want to get feedback
on this.
--
Ticket URL: <https://code.djangoproject.com/ticket/34853#comment:18>