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
When clicking on a day cell within the Drag and Drop (from outside calendar), an empty event is automatically created without providing the user an opportunity to enter the event name or any other details. This behavior is unexpected and can lead to a calendar filled with unnamed events, making it difficult to manage and understand scheduled activities.
Screen.Recording.2024-04-26.at.6.30.19.PM.mov
Expected Behavior
Clicking on a day cell should either:
Do nothing: Simply highlight the selected day without creating an event.
Trigger a modal or form: Prompt the user to input event details, including the event name, before creating the event on the calendar.
Actual Behavior
An empty event is automatically created upon clicking a day cell, leading to a calendar filled with unnamed events and potential confusion for users.
Check that this is really a bug
Reproduction link
https://jquense.github.io/react-big-calendar/examples/index.html?path=/docs/addons-drag-and-drop--example-3
Bug description
When clicking on a day cell within the Drag and Drop (from outside calendar), an empty event is automatically created without providing the user an opportunity to enter the event name or any other details. This behavior is unexpected and can lead to a calendar filled with unnamed events, making it difficult to manage and understand scheduled activities.
Screen.Recording.2024-04-26.at.6.30.19.PM.mov
Expected Behavior
Clicking on a day cell should either:
Actual Behavior
An empty event is automatically created upon clicking a day cell, leading to a calendar filled with unnamed events and potential confusion for users.
react-big-calendar version
1.11.3
React version
18.2.0
Platform/Target and Browser Versions
macOS
Validations
Would you like to open a PR for this bug?
The text was updated successfully, but these errors were encountered: