[webkit-dev] New Feature Flag Proposal: TIME_INPUT_FIELDS
yosin at google.com
Tue Jun 26 22:38:51 PDT 2012
>Will the appearances of the controls be consolidated?
No. In other words, to use different appearances among platforms, I
introduced this flag in addition to ENABLE_INPUT_TYPE_TIME.
ENABLE_TIME_INPUT_FIELDS is child flag of ENABLE_INPUT_TYPE_TIME.
When ENABLE_INPUT_TYPE_TIME w/o TIME_INPUT_FIELDS, input type "time" uses
single text field and doesn't change current behavior.
On Wed, Jun 27, 2012 at 2:19 PM, Peter Beverloo <peter at chromium.org> wrote:
> On Tue, Jun 26, 2012 at 9:20 PM, Yosi Inoue <yosin at chromium.org> wrote:
>> Hi WebKit!
>> I would like to notify adding new feature flag ENABLE_TIME_INPUT_FIELDS.
>> This flag will enable multiple fields input UI for input type "time".
>> Looking is as same as input type "number" (including spin button), but
>> each time component, hour, minute, second, millisecond, period(AM/PM), is
>> fixed and handles keyboard input as overwriting rather than inserting, like
>> Mac OSX's DateTime control.
>> This feature will be enable for desktop version of Chrome (== excluding
> Android already enables time (and date) inputs, and defers to the
> platform's input mechanisms. Will the appearances of the controls be
> This flag also introduce following class and functions:
>> * DateTimeFormat class
>> * localizedDecimalSeparator()
>> * localizedTimeFormat()
>> * localizedShortTimeFormat()
>> * DateTimeFIeldElement (for shadow DOM)
>> * DateTimeEditElement (for shadow DOM)
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev