- From: Ian Hickson <ian@hixie.ch>
- Date: Tue, 30 Jul 2013 00:43:33 +0000 (UTC)
- To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Cc: WHAT Working Group <whatwg@whatwg.org>
On Tue, 30 Jul 2013, Silvia Pfeiffer wrote: > > I actually think we need to distinguish between local and floating time > zones. > > When using datetime-local, I would actually expect that the browser > picks the local timezone as the default time zone, so doesn't expose a > timezone entry in the UI. The value that is returned by the form, > however, actually has a timezone. That's type=datetime (the time zone is always UTC). > In contrast, when the app doesn't want a timezone, the developer should > probably use something like datetime-floating. Then, it's clear that the > time zone is actually left off of the returned value, too. That's type=datetime-local. It's not only useful for floating times, as noted in the response on this bug, which is why it's not called something with "floating" in the name: https://www.w3.org/Bugs/Public/show_bug.cgi?id=17856 -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 30 July 2013 00:43:57 UTC