New issue
Advanced search Search tips

Issue 690803 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Mar 2017
Components:
EstimatedDays: ----
NextAction: 2017-02-28
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Date and Number Type stopped working in culture - Chrome/Chromium 56

Reported by ti.tahai...@gmail.com, Feb 10 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.76 Safari/537.36 OPR/43.0.2442.806

Steps to reproduce the problem:
1. Set current computer Culture in Turkey/Turkish or different from en-US.
2. And set number type default value 1000000,25 (1.000.000,25)

What is the expected behavior?
We are working in tr-TR culture format and default value must be shown as "1000,02".

What went wrong?
When I set "1000.02" default value to HTML5 number type then it is giving 1000.02. It is normal for en-US culture. But we are working in tr-TR culture format and value must be shown as "1000,02". 

When I set the value as "1000,02" it is giving an error on console.

The message is : "The specified value "1000,02" is not a valid number. The value must match to the following regular expression: -?(\d+|\d+.\d+|.\d+)([eE][-+]?\d+)? ".
This problems were created after Chrome / Chromium based browsers was updated to version 56

I think this version(56) must be used regex appropriately for the current culture.

Example Urls:
https://jsfiddle.net/tipek/3gpc2tf1/
http://dojo.telerik.com/UyIsA/21

Other issues: 
https://github.com/telerik/kendo-ui-core/issues/2751
http://www.telerik.com/forums/datepicker-and-currencytextbox-stopped-working-in-chrome-56

Thanks

Did this work before? Yes Chromium 55 <=

Chrome version: 56.0.2924.76  Channel: stable
OS Version: 10.0
Flash Version: 

I think this version(56) must be used regex appropriately for the current culture.


 
Untitled.png
207 KB View Download
Labels: Needs-Bisect Needs-Triage-M56

Comment 2 by junov@chromium.org, Feb 10 2017

Components: -Blink Blink>Forms>Number Blink>Forms>Date

Comment 3 by tkent@chromium.org, Feb 13 2017

Is your Chrome UI language Turkish?
'value' attribute must not support localized numbers/dates according to the standard, and Google Chrome haven't accepted them.
https://jsfiddle.net/tipek/3gpc2tf1/ should not work in any locales.

We should confirm and bisect http://dojo.telerik.com/UyIsA/21 .

Why that jsfiddle should'not work? Do I have to give value as "1.75"? Or can we say the only decimal seperator is dot(.) ?
We use English Language in Chrome UI but current computer culture is Turkish.

The latest update has caused us big trouble. We will have to update our systems today and we are not sure how to solve it.

I guess we have no choice, it seems we will use only input type as "Text".

Comment 6 by tkent@chromium.org, Feb 13 2017

> Why that jsfiddle should'not work?

Because the HTML standard defines so.

> Do I have to give value as "1.75"? Or can we say the only decimal seperator is dot(.) ?

Yes and yes.
As I already wrote, Google Chome haven't changed this behavior for years.


Comment 7 by tkent@chromium.org, Feb 13 2017

> We use English Language in Chrome UI but current computer culture is Turkish.

I this case, the current expected behavior of type=number and type=date is to show values in English format.  We haven't changed this behavior for years.


Comment 8 by tkent@chromium.org, Feb 13 2017

> We should confirm and bisect http://dojo.telerik.com/UyIsA/21 .

Ah, this contains |type="number" value="1000,02"|.  So, this should not work even with Google Chrome 55.

Labels: -Needs-Bisect
Tested this issue on Windows-10 using chrome latest stable M56-56.0.2924.87. By opening the link http://dojo.telerik.com/UyIsA/21 observed the console displays error saying "The specified value "1000,02" is not a valid number". 

Tested the same on older version of chrome on M35 and M40 and it displays error saying "Error while parsing the sandbox attribute", so tested on M50-50.0.2661.0 and observed similar behavior as seen on latest stable.

Comment 10 by tkent@chromium.org, Feb 13 2017

Labels: Needs-Feedback
NextAction: 2017-02-28
ti.tahaipek@, can you provide a reproducible HTML which had no problem with Google Chrome 55, and had a problem with Google Chrome 56?

FYI. Chromium binary close to Google Chrome 55 is here: https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win/423765/

Status: Archived (was: Unconfirmed)
We don't have enough information to reproduce the issue. Closing.

Sign in to add a comment