Use defaultTimezone, when a time is already set.

[apepper]

• New config field 'defaulTimezone'.

[apepper]

Also added daylight saving check, when date is change.

[trentrichardson]

Just asking to understand where this is coming from. I personally haven't worked with timezone's much, other users have contributed most of that part.

Earlier this week when I merged your changes I also added a this._defaults.timezone and set it to null. (not to be confused with this.timezone, which is the current stored value) Would that work? When it's null it will try to pull from browser, but if you pass in a timezone it will default to that.

Just curious, I don't mind merging if this is needed.

[apepper]

There are two cases:

1. when no time is set so far - use the timezone of the browser
2. when a time is already there, but no timezone is given - use the defaultTimezone.

When using this._defaults.timezone this will work for already present time sets without timezones. But if not time is given so far, it will also be used, because so far the check for local time is, if no timezone is set.

With this patch you can have both: a fixed timezone for all dates (using this._defaults.timezone) and a "preset" timezone for dates, that do not provide a timezone.

[sayap]

I am trying to make a local change so that clicking on "Now" would set the time to be the current time in the picker's timezone (if one is set), and this defaultTimezone option makes things really confusing. Consider that we don't have defaultHour, defaultMinute, etc, I am not too sure what does it bring to the table, especially with "+0000" being the default.

when a time is already there, but no timezone is given

Well, if the picker's timeFormat expects a timezone, the backend should just fill in a value with timezone. I don't think the frontend should worry about that.