- From: Ian Hickson <ian@hixie.ch>
- Date: Tue, 30 Jul 2013 02:32:05 +0000 (UTC)
- To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Cc: WHAT Working Group <whatwg@whatwg.org>
On Tue, 30 Jul 2013, Silvia Pfeiffer wrote: > On Tue, Jul 30, 2013 at 10:43 AM, Ian Hickson <ian@hixie.ch> wrote: > > 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). > > Hmm.. .what does a JS dev use, then, when they want to require a user to > have to pick a timezone other than UTC? There's no control in HTML today that exposes a time zone interface, whether it's UTC or anything else. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 30 July 2013 02:32:30 UTC