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

Overlapping zero-duration events #377

Open
hakonvik opened this issue Nov 13, 2024 · 5 comments
Open

Overlapping zero-duration events #377

hakonvik opened this issue Nov 13, 2024 · 5 comments

Comments

@hakonvik
Copy link

hakonvik commented Nov 13, 2024

Hi, this might be a rare scenario but in our usage we occasionally have events with the same start and end time. When rendered it seems they overlap even if slotEventOverlap is set to false.

Here is a codepen illustrating the issue;
https://codepen.io/hakonvik/pen/NWQoYVv

The CSS for min-height is a workaround to render an event with at least some height so that the time label is visible.

@vkurko
Copy link
Owner

vkurko commented Nov 14, 2024

If the duration of an event is zero, what do you expect to see? In timeGrid view, the height of an event is equal to its duration, so naturally the event turns into a line if the duration is zero.

@hakonvik
Copy link
Author

Thanks for your reply :)

In most calendars I'm familiar with it is possible to have an event with start end end being the same datetime, an example here from Microsoft Teams:

image

The main issue regardless of the event being a line or not is that two events having the same start and end datetime overlap when they shouldn't as far as I can see?

@vkurko
Copy link
Owner

vkurko commented Nov 29, 2024

In v3.7.1 the minimum displayed event size is fixed at the slotDuration value. Please check.

@hakonvik
Copy link
Author

hakonvik commented Dec 2, 2024

Thank you for the update. Events are now rendered with a minimum height, but is looks like they still overlap if two or more events have the same start/end.

I've updated the codepen to illustrate this using the latest version (3.7.1).

@vkurko
Copy link
Owner

vkurko commented Dec 2, 2024

I see the problem. Thank you, I'll fix it soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants