Using the new JS API with ResizeObserver to detect parent resize

[ghazette]

I had trouble with the parent resize, windows was sometimes dragged outside the parent limits, i am using it in my 3D viewer for the GUI, no problem since i implemented the ResizeObserver

[mauricius]

Thank you for the PR!

I've taken a brief look at the implementation, but I don't get the point of the handleParentResize function. Looks like that it works even without it.

[ghazette]

handleParentResize update the boundaries when parent container is resized, windows are automatically moved no click action are required on the windows

[HLN177]

I recently encountered the same issue where the draggable component overflows the boundaries of the parent container after the parent is resized. In theory, the dimensions of the parent container shouldn't be altered. If a resize listener is added to the parent component, the draggable component will recalculate its boundary values internally, which could lead to conflicts between the component's coordinates and the boundary values. I think the logic code itself needs to handle this to prevent such occurrences.

[ghazette]

I recently encountered the same issue where the draggable component overflows the boundaries of the parent container after the parent is resized. In theory, the dimensions of the parent container shouldn't be altered. If a resize listener is added to the parent component, the draggable component will recalculate its boundary values internally, which could lead to conflicts between the component's coordinates and the boundary values. I think the logic code itself needs to handle this to prevent such occurrences.

Did my patch fix this issue for you ?

[HLN177]

I recently encountered the same issue where the draggable component overflows the boundaries of the parent container after the parent is resized. In theory, the dimensions of the parent container shouldn't be altered. If a resize listener is added to the parent component, the draggable component will recalculate its boundary values internally, which could lead to conflicts between the component's coordinates and the boundary values. I think the logic code itself needs to handle this to prevent such occurrences.

Did my patch fix this issue for you ?

Your idea is good. But I finally choose to setup different "key" to force re-render the components while it could re-calculate the boundary when I need.