-
-
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
Custom drag handle not working with renderCB when using LazyLoad or React #2939
Comments
* fix gridstack#2939 * MakeWidget() will not call drag&drop init if lazy load - which is done after content is renderCB instead. * added `Utils.lazyLoad()` to make it easier to check.
fixed in next release. as for React, we shouldn't call MakeWidget() until all DOM content has been created (if you have content custom drag handler). What I do in Angular wrapper. Otherwise you have to disable/re-enable move on the widget as don't forget to donate if you find this lib useful! |
Update: |
When using
renderCB
to render elements, custom drag handles are not functioning as expected. The drag functionality remains bound to the default.grid-stack-item-content
instead of the specified custom handle.Environments where issue occurs:
lazyLoad: true
(Works fine whenlazyLoad: false
)lazyLoad: false
, likely due to React components mounting after GridStack initialization)Expected Behavior:
The custom drag handle should be functional when specified in the
renderCB
implementation.Current Behavior:
The drag functionality remains bound to
.grid-stack-item-content
instead of the custom handle.[Please let me know if you need any additional information or specific code examples to reproduce the issue.]
Screen.Recording.Feb.8.2025.mov
The text was updated successfully, but these errors were encountered: