feature requests for scheduling

[kcbraunschweig]

A couple things that would help me save a bunch of data entry time when updating the schedule for talks.

1. We know the event that a talk is submitted/accepted for, hopefully we know the dates of that event. Can the start/end dates default to the first day of that event rather than blank? Maybe not actually set to that if we want talks to start out with no assigned date but when you click on it to edit at least. That'd save time if you only have to adjust the day.
2. When a start date is set, automatically sent the end date to the same day (if it's currently unset). 99% of the time the start and end day will be the same so save re-entering it.
3. When setting a start time, if the end time is unset, set it to 1 hour later. That won't always be right, but the majority of the time it will be. Even if it's wrong it'll likely set the AM/PM correctly so it still saves a field update.
4. Drop seconds field from the times. Scheduling to the minute is good enough :)

[DrupalPhil]

This one was a tad tricky (logistically).

I tried defaulting to the date of the event but this posed issues with setting values when we didn't expect to or conflicts with the HTML5 widget.

What I landed on was this:

1. When you try to add a start date, it will restrict you to dates from the referenced event -- This at least places you in the right month when you're selected a day
2. I dropped the seconds
3. When you select a start date / time, the end date / time is set to the same day + 1 hour. This is only done when no value currently exists.

[DrupalPhil]

I've closed but this could use some legit testing. This felt a bit kludgy during development but completely safe to roll back.

[kcbraunschweig]

Thanks so much. This is MUCH better. So far the only issue I've noticed is if you enter the date via keyboard rather than with the picker. Scenario:
goal date: 03/07/2026
You enter month 03
focus moves to day
enter day 07
focus moves to year
you enter the 2 -> it immediately updates the end date to 03/07/0002
you continue entering 026

I imagine this didn't show up because you were using the picker and setting all digits of the year at the same time rather than as 4 keystrokes.

[kcbraunschweig]

Noticed that the time fields suffer from the same behavior when using keystrokes not the picker. i.e. If you intend to enter the start time as 13:45 you enter 13, tab, type the 4, it sets the end time to 14:04 before you continue to enter the 5 in 45.

[DrupalPhil]

Is this on new Sessions or existing?

On Chrome, I can't reproduce this. Are you using something else?

[DrupalPhil]

Ah, I see now. I was only looking at the start date I was editing, not the end date. Got it now.

[kcbraunschweig]

This is minor but I'll also point out that the date/time picking code seems to be duplicated from sessions to other things that get scheduled, for example node/add/special_event because the others didn't get the improvements described here that sessions did. While sessions are by far the most important, it's probably a good idea to fix all the duplicate code at the same time (or deduplicate it if possible).