Add suuport for <input type="time">
Created attachment 147186 [details] First patch
Comment on attachment 147186 [details] First patch Attachment 147186 [details] did not pass mac-ews (mac): Output: http://queues.webkit.org/results/12939855
(In reply to comment #1) > Created an attachment (id=147186) [details] > First patch What do you think about UI in a page? How does a user invoke TimeChooser?
Please use ENABLE_TIME_CHOOSER for enabling this feature. Some port, e.g. Android, enables ENABLE_TIME_INPUT but they may not want to use time chooser.
(In reply to comment #4) > Please use ENABLE_TIME_CHOOSER for enabling this feature. > Some port, e.g. Android, enables ENABLE_TIME_INPUT but they may not want to use time chooser. There is an ENABLE_CALENDAR_PICKER used in WebCore/html/DateInputType.cpp
I was thinking of modeling it on color chooser implementation (haven't uploaded a patch but have it on my branch). But when I saw the bug that Yosin was working, wanted to wait for that before proceeding with that.
(In reply to comment #3) > (In reply to comment #1) > > Created an attachment (id=147186) [details] [details] > > First patch > > What do you think about UI in a page? How does a user invoke TimeChooser? I was thinking of modeling it on color chooser implementation (haven't uploaded a patch but have it on my branch). But when I saw the bug that Yosin was working, wanted to wait for that before proceeding with that.
(In reply to comment #5) > (In reply to comment #4) > > Please use ENABLE_TIME_CHOOSER for enabling this feature. > > Some port, e.g. Android, enables ENABLE_TIME_INPUT but they may not want to use time chooser. > > There is an ENABLE_CALENDAR_PICKER used in WebCore/html/DateInputType.cpp If I am understanding it correctly, you are suggesting that this feature that delegates the UI to the client in another flag similar to CALENDAR_PICKER?
(In reply to comment #8) > (In reply to comment #5) > > (In reply to comment #4) > > > Please use ENABLE_TIME_CHOOSER for enabling this feature. > > > Some port, e.g. Android, enables ENABLE_TIME_INPUT but they may not want to use time chooser. > > > > There is an ENABLE_CALENDAR_PICKER used in WebCore/html/DateInputType.cpp > > If I am understanding it correctly, you are suggesting that this feature that delegates the UI to the client in another flag similar to CALENDAR_PICKER? I meant be * be wrapped * in another flag
(In reply to comment #9) > (In reply to comment #8) > > (In reply to comment #5) > > > (In reply to comment #4) > > > > Please use ENABLE_TIME_CHOOSER for enabling this feature. > > > > Some port, e.g. Android, enables ENABLE_TIME_INPUT but they may not want to use time chooser. > > > > > > There is an ENABLE_CALENDAR_PICKER used in WebCore/html/DateInputType.cpp > > > > If I am understanding it correctly, you are suggesting that this feature that delegates the UI to the client in another flag similar to CALENDAR_PICKER? > > I meant be * be wrapped * in another flag Yes, please use another flag something like ENABLE_TIME_PICKER, or another appropriate one.
For desktop browsers, inline editing UI which yosin is working on is enough and picker dialog UI would be unnecessary (or optional). On the other hand, we want picker dialog UI for mobile browsers, and no inline editing UI. iOS and Chromium/Android have picker dialog UI for date/time types. So, both of inline editing UI and picker dialog UI should have their own ENABLE flags. I think we can make generic API of picker dialog UI for all of date/time types. We currently have PAGE_POPUP API in ChromeClient for CALENDAR_PICKER, however we might able to change CALENDAR_PICKER so that it uses the generic API and PAGE_POPUP API is one of implementations of the generic API.
Comment on attachment 147186 [details] First patch Please apply * ENABLE_INPUT_MULTIPLE_FIELDS_UI or * No ENABLE_INPUT_MULTIPLE_FIELDS, and support ChromeClient::openDateTimeChooser