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
On month view if I dodubleclick on event, onDoubleClickEvent is triggered, if I doubleclick on slot, then onSelectSlot is triggered, which is perfect.
But on day and week view on container with all day, if I click there on event, first the onSelectSlot function is triggered and after that onDoubleClickEvent function. Which means it works completely different than in other places on calendar.
Expected Behavior
Should trigger only onDoubleClickEvent when clickng on event in allDay section on month and day view
goskan93
changed the title
Week and Day view all day slots double clicks are detected faster that event click is I click on all day event
Week and Day view all day slots double clicks are detected faster that event click if I click on all day event
Jan 24, 2025
goskan93
changed the title
Week and Day view all day slots double clicks are detected faster that event click if I click on all day event
Week and Day view, all day container triggers onSelectSlot before onDoubleClickEvent when I click on event
Jan 24, 2025
Check that this is really a bug
Reproduction link
.
Bug description
I have calendar with onDoubleClickEvent and onSelectSlot props defined
On month view if I dodubleclick on event, onDoubleClickEvent is triggered, if I doubleclick on slot, then onSelectSlot is triggered, which is perfect.
But on day and week view on container with all day, if I click there on event, first the onSelectSlot function is triggered and after that onDoubleClickEvent function. Which means it works completely different than in other places on calendar.
Expected Behavior
Should trigger only onDoubleClickEvent when clickng on event in allDay section on month and day view
Actual Behavior
No response
react-big-calendar version
1.16.3
React version
18.2.0
Platform/Target and Browser Versions
Windows, Chrome 131.0.6778.265
Validations
Would you like to open a PR for this bug?
The text was updated successfully, but these errors were encountered: