On Tue, Jun 18, 2013 at 5:33 PM, RjOllos <[email protected]> wrote: > Okay, I'm seeing the same thing after following your steps. I wonder if this > can be considered a bug then, or if it is rather just the intended behavior > of the datetime picker when it receives an invalid input?
Humm, I think that is the intended behavior. The timezoneList option defines available timezone offsets. Because an input isn't in the list, the time picker reset to default. The latest v1.3 time picker has the same behavior [1]. Currently, the timezone list for time picker is generated from available timezones [2]. If no pytz, the timezones are full hours from -12:00 to +12:00 [3]. 1. http://trentrichardson.com/examples/timepicker/ 2. http://trac.edgewall.org/browser/branches/1.0-stable/trac/util/datefmt.py#L363 3. http://trac.edgewall.org/browser/branches/1.0-stable/trac/util/datefmt.py#L887 -- Jun Omae <[email protected]> (大前 潤) -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/groups/opt_out.
