Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Day boundaries on agenda page should show day names in the locally selected time #3323

Closed
ietf-svn-bot opened this issue Jun 29, 2021 · 3 comments · Fixed by #5282
Closed

Comments

@ietf-svn-bot
Copy link

type_defect | by [email protected]


Where I live, "Local Time" gets the day wrong. The day headings (like "Monday, July 26, 2021") need to follow the time zone, even if the session names (like "Monday Session I") stay the same.


Issue migrated from trac:3323 at 2022-03-04 08:44:43 +0000

@ietf-svn-bot
Copy link
Author

@[email protected] changed status from new to accepted

@ietf-svn-bot
Copy link
Author

@[email protected] commented


This isn't quite as straightforward as it might seem at first blush.

If you happen to live in a timezone where the active meeting times cross a day boundary, what to display becomes difficult.

For instance, if the first set of sessions would normally run from Sun pm through Mon am in your local timezone, should the header line you point to always say Sunday? What if you've only selected sessions that would occur on Monday?

The current code tries to thread this needle by putting all the localization in each session's row. Letting it leak out to some other, but not all, places will add a new potential source for confusion.

@vttale
Copy link

vttale commented Mar 3, 2023

I wasn't sure whether this is the same issue I'm having with the current agenda, but it seems closely related at least. For the Yokohama meeting I will be participating remotely from US/Eastern. When I look at the agenda, it titles sections in way that is definitely inconsistent with the way that on-site participants will refer to session blocks.

Like, dispatch, which is traditionally in the first session of the week, is in something now called "Sunday Session 1". Okay, whatever, I can make a certain sort of sense of that even though it isn't what onsite people would call it. It then gets the titles of Monday sessions 2 through 4 right, ... but, then calls Tuesday Session 1 as Monday Session 1, undoubtedly for the same reasons that the Sunday Session 1 thing arises but making less of that certain sort of sense on a day that already had three sessions before it.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 14, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants