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

Drag selection not working properly when moving upwards #2535

Open
4 of 5 tasks
sile95 opened this issue Mar 13, 2024 · 3 comments
Open
4 of 5 tasks

Drag selection not working properly when moving upwards #2535

sile95 opened this issue Mar 13, 2024 · 3 comments
Labels

Comments

@sile95
Copy link

sile95 commented Mar 13, 2024

Check that this is really a bug

  • I confirm

Reproduction link

https://jquense.github.io/react-big-calendar/examples/index.html?path=/docs/examples--example-2

Bug description

Screen.Recording.2024-03-13.at.11.07.05.mov

Hey guys,

There appears to be an issue with selection when trying to select timeslots and moving upwards.
Its even happening in your own examples, so i've added that link to reproduce it easily, as well as video to display it. Just start adding timeslot and start moving upwards, it will change the start to 00:00

Note: I am also having this issue when i bundled it with rollup and used it in my UI-components lib, but when i install it directly in the app, it works fine, could be some issue with react-big-calendar and rollup?

Expected Behavior

When selecting timeslots upwards, it shouldnt move the start selection to 00:00

Actual Behavior

When used timeslot selection it moves the start slot all the way up to 00:00

react-big-calendar version

1.11.0

React version

18.2.0

Platform/Target and Browser Versions

Chrome 122.0.6261.94, Mozila 123.0.1, Safari 17.2.1

Validations

  • Read the docs.
  • Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
  • Make sure this is a react-big-calendar issue and not an implementation issue

Would you like to open a PR for this bug?

  • I'm willing to open a PR
@sile95 sile95 added the bug label Mar 13, 2024
@jay-atlasopen

This comment was marked as resolved.

@forceddd
Copy link
Contributor

forceddd commented Apr 2, 2024

@jay-atlasopen @sile95 This bug is resolved in #2545

@forceddd
Copy link
Contributor

@jay-atlasopen @sile95 This issue has been fixed in version 1.11.6

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

No branches or pull requests

3 participants