[Webkit-unassigned] [Bug 59752] Allow Localized Date Strings for Date Input Fields
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Apr 28 19:19:02 PDT 2011
https://bugs.webkit.org/show_bug.cgi?id=59752
--- Comment #9 from Kent Tamura <tkent at chromium.org> 2011-04-28 19:19:02 PST ---
(In reply to comment #7)
> Arg. This is a good point. And raises an issue. Currently I added the following:
>
> // If the input string is valid this function returns a valid
> // HTML5 date string for the specified type. HTML5 date strings
> // are a subset of ISO-8601.
>
> However, I could instead have the function return a DateComponents object,
> That would match the format function. Or a double value, representing
> the milliseconds since the 1970 epoch (which can then be serialized
> pretty easily by BaseDateTimeInputType. Do you have a preference for
> once of the other types?
Probably the double value is simpler.
(In reply to comment #8)
> Hopefully I didn't step on your toes with: <http://webkit.org/b/29359>,
> which I see you said you've started working on.
I'm working on webkit.org/b/53961 and it won't cover the text field localization. This patch is very helpful. Thank you.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list