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
Timed event from previous day causes incorrect +more count dayMaxEventRows based on calendar width and event order #6608
Comments
Thanks, confirmed. I reduced the events and it seems the timed event on the 31 is causing that: https://codepen.io/acerix/pen/oNeeNXq?editors=001 I didn't find a good workaround, but it seems to work correctly if the events are ordered differently: |
Thanks a lot for your prompt reply, should we expect a fix in the near future? |
Any new fix? we are still struggling with this issue! |
we are still waiting a fix for the above issue. |
This is rather critical for a calendar to have proper chronological events. |
is this being worked on or we should give up on a fix ? the impact on the calendar app is making the tool useless |
any updates? this is critical for usage |
Fixed in v6.1.11 Updated repro: |
Reduced Test Case
https://codepen.io/YDeeb/pen/wvqeZPe
Bug Description
Hello, I'm facing an issue when using 'dayMaxEventRows: true', sometimes the '+more' label and its popover don't show the correct events count and render.
Considering the case of the events in the reduced test case, the fullcalendar container width is 600px, on Oct 1st/2nd cell for example, the '+more' label is showing +1 and when clicking on it you'll notice that the popover is showing one event only.
The correct behavior should be +2 and popover should show 2 events.
Another thing is that when you further reduce the width (to 400px for example), you'll notice that the '+more' label/popover is behaving correctly.
Thanks in advance.
Screenshots
The text was updated successfully, but these errors were encountered: