IETF extended language subtag not understood by Chromium
Reported by
c933...@gmail.com,
May 9 2018
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Linux; Android 8.0.0; G8441 Build/47.1.A.8.49) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.137 Mobile Safari/537.36 Steps to reproduce the problem: 1. Have a locale code like zh-yue-hant that include the extended language tag 2. Use methods like toLocaleString(locale) to tell the browser use the particular locale What is the expected behavior? Browser be able to understand the locale string What went wrong? Being ignored? See discussions at https://github.com/KC3Kai/KC3Kai/pull/2563#issuecomment-387831301 Did this work before? N/A Chrome version: 64.0.3282.137 Channel: n/a OS Version: Flash Version: See discussion at https://github.com/KC3Kai/KC3Kai/pull/2563#issuecomment-387831301
,
May 10 2018
,
May 16 2018
c933103@ -- Thanks for reporting this issue. Could you please share any sample test case or HTML file to reproduce the issue at Chrome TE's end. This would help us in triaging the issue further. Thanks!
,
May 28 2018
Hi, Thank you for flagging. This is more on Engineering case. Looping in Engineering Team for assistance. Regards!
,
Nov 21
**UI mass Triage** We were unable to find repro steps for this bug as per c#3. If you have more data to reproduce this bug on chrome latest versions(M70-70.0.3538.110 or M71) or have clear repro steps, please reopen or file a new issue. Thanks! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by krajshree@chromium.org
, May 10 2018