- From: TAMURA, Kent <tkent@chromium.org>
- Date: Fri, 16 Nov 2012 09:59:39 +0900
- To: Mounir Lamouri <mounir@lamouri.fr>
- Cc: whatwg <whatwg@lists.whatwg.org>
I think I can do it for WebKit if WHATWG specification and W3C specification are changed so. On Thu, Nov 15, 2012 at 2:23 AM, Mounir Lamouri <mounir@lamouri.fr> wrote: > On 13/11/12 09:42, TAMURA, Kent wrote: >> The current UI implementations of Opera, iOS, and Chrome-Android spoil >> the >> HTML standard. Web authors hardly have motivation to use type=datetime. >> They can add 'UTC' text, and their code can append 'Z' to values easily. >> I agree that the type names are not good. People must think >> type=datetime >> is a combination of type=date and type=time. It's not too late to rename >> datetime-local to datetime because the number of type=datetime or >> type=datetime-local in the Web is terribly smaller than the number of >> type=date. > Tamura, do you think Webkit/Chrome can do this change? > Gecko/Mozilla would be willing to implement 'datetime' that way and not > implement 'datetime-local' but having other vendors committed to this > change would be helpful and prevent us from going alone in this path. > Cheers, > -- > Mounir -- TAMURA Kent Software Engineer, Google
Received on Friday, 16 November 2012 01:08:24 UTC