RESOLVED FIXED98983
[Chromium] Calendar picker: should use consistent Localizer object
https://bugs.webkit.org/show_bug.cgi?id=98983
Summary [Chromium] Calendar picker: should use consistent Localizer object
Kent Tamura
Reported 2012-10-10 20:28:18 PDT
Calendar picker: should use consistent Localizer object In WebKit/chromium/src/DateTimeChooserImpl.cpp, we use two Localizer objects, one if m_localizer and another is 'localizer' local object in writeDocument. We should use single Localizer object.
Attachments
Patch (3.30 KB, patch)
2012-10-10 20:33 PDT, Kent Tamura
no flags
Kent Tamura
Comment 1 2012-10-10 20:33:11 PDT
Kentaro Hara
Comment 2 2012-10-10 20:37:50 PDT
Comment on attachment 168133 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=168133&action=review Looks reasonable > Source/WebKit/chromium/ChangeLog:15 > + environment; e.g. Month labels in a calendar picker were numeric. This > + patch fixes it, and this is covered by > + fast/forms/date/calendar-picker-appearance.html. No change in the test result? Or you might want to add a new test that covers this change.
Kent Tamura
Comment 3 2012-10-10 20:41:15 PDT
Comment on attachment 168133 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=168133&action=review >> Source/WebKit/chromium/ChangeLog:15 >> + fast/forms/date/calendar-picker-appearance.html. > > No change in the test result? Or you might want to add a new test that covers this change. The test is already marked as failure in TestExpectations. I won't add image results to this patch because I don't have handy Linux (ICU) environment.
Kentaro Hara
Comment 4 2012-10-10 20:41:47 PDT
Comment on attachment 168133 [details] Patch Makes sense.
WebKit Review Bot
Comment 6 2012-10-10 21:44:48 PDT
Comment on attachment 168133 [details] Patch Clearing flags on attachment: 168133 Committed r131011: <http://trac.webkit.org/changeset/131011>
WebKit Review Bot
Comment 7 2012-10-10 21:44:52 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.