grid re-initing messes up widget ordering after widget was removed

[AdmiralSnyder]

Subject of the issue

I am rendering the context of the div manually and have to re-init the grid after doing widget removals
But there's a bug in the re-initing for which i wrote a repro, see below. that has instructions and buttons to press,
here is a 20s video of the immediate repro of the issue:

GridStackErrorReproReinitShort.mp4

here's a screenshot:

Your environment

• version of gridstack.js

• 12.3.3

• which browser/OS

• MS Edge on Windows 11
• Orion (webkit based) on a macbook

Steps to reproduce

here's the demo:
https://stackblitz.com/edit/gridstack-demo-hbv1drk7?file=index.html&file=script.js

• click button 2
• observe that the widget "Third" goes away
• click button 3
• observe that the widget "Fourth" moved left

Expected behavior

re-initing a grid should not move the widgets if the grid is in float mode and the widgets are declared in the html markup.

full video

this is the full play-through of the repro, as a video:

GridStackErrorReproReinitFull.mp4

[adumesny]

I see the issue. an optimization I have to not write certain 'default' values back (x:0 or y:0) are causing w4 to be autoplacement since one coordinate is missing...

[adumesny]

fixed in next release. don't forget to donate if you find this lib useful!

[AdmiralSnyder]

thank you, is there an eta for that next release?

[AdmiralSnyder]

quick followup question @adumesny : i just realized yesterday that gridstack is keeping traces of the width (and supposedly the height) of widgets, too, and writes them back to the dom when re-initing... has this been mitigated in the bugfix for this issue?

(i had to manually render out a second pair of attributes to my dom nodes) and write those values into gs-w and gs-h while doing the missing-zeroes fix)