New issue
Advanced search Search tips

Issue 883253 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Nov 28
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug

Blocked on:
issue 369218



Sign in to add a comment

Intl.DateTimeFormat with Estonian (et) locale - 'short/long' month output wrong

Reported by ranno.ka...@gmail.com, Sep 12

Issue description

Steps to reproduce the problem:
1. console.log in Android Chrome:
Intl.DateTimeFormat('et', { month: 'long' }).format()

What is the expected behavior?
'long' and 'short' month formats should display 'sept' or 'september'

What went wrong?
Format result is 'M09'

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 69.0.3497.91  Channel: stable
OS Version: 8.1.0
Flash Version:
 
I have tried to replicate this on many other combinations of OS/browser:
android + mozilla, ios + chrome/safari, pc + chrome, osx + safari/chrome

The bug doesn't appear on any of these, only in Android + Chrome
Components: Blink>JavaScript>Internationalization
Labels: Needs-triage-Mobile
Cc: chelamcherla@chromium.org
Labels: Target-71 M-71 Triaged-Mobile FoundIn-71
Status: Untriaged (was: Unconfirmed)
Tested the issue in Android and able to reproduce the issue. 

Steps Followed:
1. Launched chrome 
2. In chrome devtools console typed Intl.DateTimeFormat('et', { month: 'long' }).format() and observed result as 'M09'

Chrome versions tested:
60.0.3072.0 , 69.0.3497.100 , 71.0.3555.0

OS:
Android 9.0.0

Android Devices:
Pixel 2

Issue is seen in from older M-60 builds, hence considering this issue as Non-Regression and marking as Untriaged for further inputs from dev team.

Thanks!

Owner: js...@chromium.org
Jungshik looks like this is a problem with missing data. Can you please take a look?
Status: Assigned (was: Untriaged)
Blockedon: 369218
That's because Android Chrome does not have locale data for Estonian and falls back to root locale. 

See  bug 864739  (not directly related because it's about locale variant support) and bug  369218 (directly related, but long standing issue with no clear sight of resolution). 

Labels: -M-71 -Target-71
Not likely to be solved in M71. 
> Not likely to be solved in M71. 

See bug 879228 and bugs blocked by it. Actually, we may finally see some light at the end of this long tunnel. 

Labels: -Pri-2 Pri-3
Status: Fixed (was: Assigned)

Sign in to add a comment