When looking at that "time_ranges" example, when you choose a date/time/timezone in the first input field, it loads the second end datetime field with the date and time one hour later, but for some reason the timezone isn't set to the same as the start input field. Ideally, it should match whatever the start date/time/zone is set to, just one hour later in the same timezone.
When looking at that "time_ranges" example, when you choose a date/time/timezone in the first input field, it loads the second end datetime field with the date and time one hour later, but for some reason the timezone isn't set to the same as the start input field. Ideally, it should match whatever the start date/time/zone is set to, just one hour later in the same timezone.