-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Invalid drag offset when page scrolled after 9.3 #2491
Comments
Possibly related to changes in b559a6f ? |
@VincentMolinie can you please take a look. yeah scrolled content is something I didn't try before... |
I do reproduce, I will try to check what's going on |
great thank you, as I was going to revert your changes until we have time to fix it otherwise. It's holding other changes I need for work and depend on scroll so can't use 9.3.0 right now |
Okey I think I got the fix, I'll create a PR |
And the fix is here: #2499 |
I confirm that the fix is effective and solve the issue. |
@Jenny3107 you manually pulled Vincent fix and tried that ? I'm not sure it's the right fix anyway, but away this week so limited access to work on this. |
No indeed sorry, I thought it had been put on the "master" branch, I just redid an "npm install" thinking the fix had been added. I tried directly on the site: https://gridstackjs.com/demo/web2.html |
…n element (gridstack#2263)" re-opens gridstack#1275, and fix gridstack#2498 gridstack#2497 gridstack#2491 This reverts commit b559a6f.
…n element (gridstack#2263)" re-opens gridstack#1275, and fix gridstack#2498 gridstack#2497 gridstack#2491 This reverts commit b559a6f.
Subject of the issue
Trying to move widgets while the page is scrolled down lead to unexpected behavior.
It seems there is a noticeable vertical offset between the mouse position and the widget position, which get worse the lower you scroll down the page.
While at the top of the page (no scroll), there is no issue.
Example:
Your environment
Official demo: https://gridstackjs.com/demo/
Latest release is 9.3.0 at this date, which I suppose the demo is using.
Steps to reproduce
The text was updated successfully, but these errors were encountered: