In Chromium-win, we use LocaleICU for <input type=number> localization. We should apply Windows locale system instead.
Created attachment 156594 [details] Patch
Comment on attachment 156594 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=156594&action=review morrita-san: I'm not familiar with the implementation... Would you take a look? > Source/WebKit/chromium/tests/LocaleWinTest.cpp:385 > + testNumbers(ArabicEG); Let's add testNumbers(FrenchFR) and testNumbers(EnglishUS).
Comment on attachment 156594 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=156594&action=review >> Source/WebKit/chromium/tests/LocaleWinTest.cpp:385 >> + testNumbers(ArabicEG); > > Let's add testNumbers(FrenchFR) and testNumbers(EnglishUS). They are covered by the testNumberIsReversive calls with extra shouldHave argument.
Comment on attachment 156594 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=156594&action=review > Source/WebCore/platform/text/LocaleWin.cpp:756 > + negativeSuffix = negativeSign; Is this fall-through intentional? If so, please add a comment. > Source/WebCore/platform/text/LocaleWin.cpp:758 > + negativeSuffix = " " + negativeSign; Ditto.
Comment on attachment 156594 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=156594&action=review >> Source/WebCore/platform/text/LocaleWin.cpp:756 >> + negativeSuffix = negativeSign; > > Is this fall-through intentional? If so, please add a comment. oh, it's a real bug.
Created attachment 156596 [details] Patch 2 Add breaks
Committed r124735: <http://trac.webkit.org/changeset/124735>