Issue metadata
Sign in to add a comment
|
<input type='date'> doesn't use the user's locale
Reported by
johannes...@yworks.com,
Jan 25 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Example URL: http://www.w3schools.com/html/tryit.asp?filename=tryhtml_input_date Steps to reproduce the problem: 1. Have your regional settings set to a date format other than the US format (mm/dd/yyyy) 2. Have an input element with type date on the site What is the expected behavior? The displayed date format follows the user's regional settings ("locale"), instead of displaying the date as mm/dd/yyyy. What went wrong? The date inside the input element is displayed in US format. Either this is hard-coded, despite reports to the contrary (https://developers.google.com/web/updates/2012/08/Quick-FAQs-on-input-type-date-in-Google-Chrome), or this does not use the user's regional settings correctly. In my case I'm using German with ISO 8601 dates, so dd.mm.yyyy would be slightly more correct but still wrong, and yyyy-mm-dd would be correct. However, my *UI language* is en-US. If I had to guess I'd assume that Chrome incorrectly uses the UI language to format the date instead of the locale. On Windows those two things are separate, while Unix-like systems munge them together in a single language identifier. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? No Does this work in other browsers? No Edge Chrome version: 55.0.2883.87 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 24.0 r0
,
Jan 25 2017
,
Jan 26 2017
Google Chrome respects to the system locale setting only if the system locale and the Chrome UI language match. It's an intentional behavior. We have a plan to switch to content locale. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by chrishtr@chromium.org
, Jan 25 2017