Re: [webkit-dev] Please do not enable ENABLE_INPUT_TYPE_DATETIME
Unfortunately I don't have data on mobile-targeted sites. The number '0.08% of input[type=date]' came from Google's web search repository. So it is basically on desktop-targeted sites. On Tue, Jan 22, 2013 at 5:54 PM, Maciej Stachowiak wrote: On Jan 22, 2013, at 12:32 AM, "TAMURA, Kent" wrote: > > >> The two mail threads bounce back and forth between Hixie's opinion and >> yours. Was there a conclusion reached anywhere on what to do with datetime >> and datetime-local? > > We agreed that existing implementations of input[type=datetime] were wrong. > But we have no > conclusion of the type renaming and the expected UI. > So, I don't think we can provide reasonable implementation of > input[type=datetime] in WebKit > anytime soon, and we had better stop shipping the wrong implementation > before it is used widely. Do we have any data on how much usage there is currently (most particularly on mobile-targeted sites)? Regards, Maciej -- TAMURA Kent Software Engineer, Google ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Please do not enable ENABLE_INPUT_TYPE_DATETIME
On Jan 22, 2013, at 12:32 AM, "TAMURA, Kent" wrote: > > >> The two mail threads bounce back and forth between Hixie's opinion and >> yours. Was there a conclusion reached anywhere on what to do with datetime >> and datetime-local? > > We agreed that existing implementations of input[type=datetime] were wrong. > But we have no > conclusion of the type renaming and the expected UI. > So, I don't think we can provide reasonable implementation of > input[type=datetime] in WebKit > anytime soon, and we had better stop shipping the wrong implementation > before it is used widely. Do we have any data on how much usage there is currently (most particularly on mobile-targeted sites)? Regards, Maciej ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Please do not enable ENABLE_INPUT_TYPE_DATETIME
The two mail threads bounce back and forth between Hixie's opinion and yours. Was there a conclusion reached anywhere on what to do with datetime and datetime-local? We agreed that existing implementations of input[type=datetime] were wrong. But we have no conclusion of the type renaming and the expected UI. So, I don't think we can provide reasonable implementation of input[type=datetime] in WebKit anytime soon, and we had better stop shipping the wrong implementation before it is used widely. -- TAMURA Kent Software Engineer, Google ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Please do not enable ENABLE_INPUT_TYPE_DATETIME
Please do not enable ENABLE_INPUT_TYPE_DATETIME to ship implementation in your products. What do you recommend for products that have shipped it already? I recommend to disable it in the next release of the products. I'll disable it for Android Chrome. It's an incompatible change. However I think it won't have large impact because the number of input[type=datetime] in the web is only 0.08% of the number of input[type=date] -- TAMURA Kent Software Engineer, Google ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Please do not enable ENABLE_INPUT_TYPE_DATETIME
On Jan 20, 2013, at 9:55 PM, "TAMURA, Kent" wrote: > Please do not enable ENABLE_INPUT_TYPE_DATETIME to ship type=datetime>implementation in your products. What do you recommend for products that have shipped it already? - Maciej ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Please do not enable ENABLE_INPUT_TYPE_DATETIME
On Sun, Jan 20, 2013 at 9:55 PM, TAMURA, Kent wrote: > Please do not enable ENABLE_INPUT_TYPE_DATETIME to ship type=datetime>implementation in your products. > > We had some discussion in WHATWG [1] [2] and realized > UIs in iOS Safari and Android Chrome are wrong and harmful. The current > code for in WebCore can't make a reasonable UI and > should not be shipped in products. > The two mail threads bounce back and forth between Hixie's opinion and yours. Was there a conclusion reached anywhere on what to do with datetime and datetime-local? I don't think just asking people to disable ENABLE_INPUT_TYPE_DATETIME will get us far (why risk breaking existing websites without a minimum of data?). Can you share the plan going forward? Benjamin ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Please do not enable ENABLE_INPUT_TYPE_DATETIME
Please do not enable ENABLE_INPUT_TYPE_DATETIME to ship implementation in your products. We had some discussion in WHATWG [1] [2] and realized UIs in iOS Safari and Android Chrome are wrong and harmful. The current code for in WebCore can't make a reasonable UI and should not be shipped in products. For other new input types, they are ready to implement platform-specific code. We're going to post an implementation guide or make a wiki page to explain what is needed. [1] http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Nov/thread.html#msg119 [2] http://lists.w3.org/Archives/Public/public-whatwg-archive/2013Jan/thread.html#msg45 -- TAMURA Kent Software Engineer, Google ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
