[Webkit-unassigned] [Bug 62939] A comma is being inserted into the text of a "number" field

Tue Jun 21 22:59:51 PDT 2011

https://bugs.webkit.org/show_bug.cgi?id=62939

Eric Cain <arcain at unitedbinary.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |arcain at unitedbinary.com

--- Comment #2 from Eric Cain <arcain at unitedbinary.com>  2011-06-21 22:59:51 PST ---
This is arcain from SO; thanks for submitting this bug report. I had been in the process of trying to reproduce the issue on Windows and Ubuntu with the lastest Webkit sources, but neither platform exhibited the issue, plus it took forever to build out test environments. When I looked closer, the LocalizedNumber* sources didn't even seem to be included in the build -- they were, however included in chromium. So, I was a bit confused over whether the issue was really webkit, or if it was chromium.
(In reply to comment #0)
> A comma is being inserted into the text of a "number" field. According to the HTML5 standard (http://www.whatwg.org/specs/web-apps/current-work/multipage/number-state.html#number-state):
> 
> "The algorithm to convert a number to a string, given a number input, is as follows: Return a valid floating point number that represents input."
> 
> A user named "arcain" at Stack Overflow claims to have pinpointed the problem in Webkit and has a solution (see the top answer):
> 
> http://stackoverflow.com/questions/5345095/chrome-auto-formats-input-number
> 
> I was unable to find a bug report on the issue or contact information for arcain, and since I've been having the same problem I figured I'd write a bug report and point to his solution/analysis.
> 
> I also want to add that I can see the benefit of the formatting in some cases (so maybe it should be configurable), but developers should be able to turn it off. Since there is no "year" field in HTML5, it seems logical to use number instead, but with the comma, developers are unable to do that and there is no way for them (at least from what I know) to use a year field that is just a spinbox with a number in it.
> 
> Side note, the bug is also reported in Chrome here: http://code.google.com/p/chromium/issues/detail?id=78520

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.