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
As we can see in example we have problem with scroll, there are some "lags" and "shifting"/"jumps" (hard to explain) when we want to resize event to top or bottom. And due to this fact, we cannot smoothly with good experience resize an event.
@cutterbl@AmitRDesai#2230 really should have been behind the enableAutoScroll flag. The resulting implementation is somewhat un-intuitive, seeing as the scroll to top is very sensitive. Most controls increase scroll to top/bottom speed as you drag closer to the edge, whereas the scroll speed here is static (or at least feels that way) (unsure there is a way to get the sensitivity gradient just right in pure JS).
I'm having a bit of trouble threading the enableAutoScroll prop through from the Calendar component to this one, but it would be much appreciated if there was a way to disable this behavior. As it's currently implemented, the sensitivity/jumpiness means that the predictability is preferred over having the auto-scroll behavior zoom your even to the top (or worse, quickly adjusting the event's size during the scroll to the top).
For now, I'm relying on yarn patch to comment out this behavior.
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-2
Bug description
As we can see in example we have problem with scroll, there are some "lags" and "shifting"/"jumps" (hard to explain) when we want to resize event to top or bottom. And due to this fact, we cannot smoothly with good experience resize an event.
Expected Behavior
No response
Actual Behavior
No response
react-big-calendar version
1.8.1
React version
18
Platform/Target and Browser Versions
Google Chrome
Validations
Would you like to open a PR for this bug?
The text was updated successfully, but these errors were encountered: