Closed Bug 1593590 Opened 5 years ago Closed 5 years ago

<input type="date"> visual format doesn't respect locale

Categories

(Core :: Layout: Form Controls, defect)

72 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1429578

People

(Reporter: toastal, Unassigned)

Details

User Agent: Mozilla/5.0 (Android 10; Mobile; rv:70.0) Gecko/70.0 Firefox/70.0

Steps to reproduce:

I visited a test page I made <html lang="en-US"><body><input type="date"/></body></html>.

I just downloaded a fresh copy of en-US Developer Edition. I had environment variables LANG=en_US.UTF-8 & LC_TIME=en_DK.UTF-8 & LANGUAGE=en_US:en, and config setting intl.regional_prefs.use_os_locales = true & intl.accept_languages = en-us,en,th , .

Actual results:

The input had a visual date formatting of dd/mm/yyyy, but still had the correct value.

Expected results:

Considering the LC_TIME=en_DK.UTF-8 and intl.regional_prefs.use_os_locales, I expected to see the format of yyyy-mm-dd respecting my OS settings. Alternatively and although not desired, considering the language version downloaded, the language attribute on the page, intl.accept_languages, and the LANG/LANGUAGE env vars, I expected mm/dd/yyyy.

People often seem confused by the month vs day thing, I too, expected it to at least follow one of these lines of logic for the default format; there's nothing in my scenario suggesting I wanted the dd/mm/yyyy format.

Summary: <input type="date"> doesn't respect locale → <input type="date"> visual format doesn't respect locale

When I tried Firefox with intl.regional_prefs.use_os_locales = false I got the same results.

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Layout: Form Controls
Product: Firefox → Core

Zibi, is this a dup of bug 1429578?

Flags: needinfo?(gandalf)
Flags: needinfo?(gandalf)

Thanks!

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.