You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See /meeting/110/agenda/[email protected]/prelim110/edit/ and note the thu 1500 rtgarea/rtgwg shared session.
This issue has been present for awhile, but was highlighted after a6e08f1. (Liz - you won't see this until a release with a6e08f1 in it is put into production).
This may be on purpose though - sometimes when we put multiple sessions in a single timeslot the intent is that they run in parallel, and sometimes they run sequentially, so Liz - do you want it to show a potential overflow even if in the parallel case the combined sessions will fit? We have no way to know if the intent is parallel or sequential, so right now the view acts as if such things are always sequential. Is that the right choice?
Issue migrated from trac:3319 at 2022-03-04 08:44:18 +0000
The text was updated successfully, but these errors were encountered:
Email conversations say to remove the overfull indicator when the only reason is sessions sharing a timeslot, but to keep it if there is a session that is longer than the timeslot can hold.
type_defect
| by [email protected]See /meeting/110/agenda/[email protected]/prelim110/edit/ and note the thu 1500 rtgarea/rtgwg shared session.
This issue has been present for awhile, but was highlighted after a6e08f1. (Liz - you won't see this until a release with a6e08f1 in it is put into production).
This may be on purpose though - sometimes when we put multiple sessions in a single timeslot the intent is that they run in parallel, and sometimes they run sequentially, so Liz - do you want it to show a potential overflow even if in the parallel case the combined sessions will fit? We have no way to know if the intent is parallel or sequential, so right now the view acts as if such things are always sequential. Is that the right choice?
Issue migrated from trac:3319 at 2022-03-04 08:44:18 +0000
The text was updated successfully, but these errors were encountered: