Pit Friedrich
85bb0c8c0b
CI / build-and-test (pull_request) Successful in 1m17s
The layout was saved to localStorage, but restoring it did not reliably reproduce it: - restore() applied the saved nodes one by one via grid.update(). A later item could collide with one already put back and push it off its saved spot, and nothing moved it back — so the restored layout was not the one the user left. Use grid.load(nodes, false) instead: it sorts the nodes, removes them from the engine before re-placing them, and runs in a single batch. addRemove is off because Flow owns which children exist. - gridstack's save() omits w/h when they are 1. The manual restore passed them through as undefined, and the server read them as 0 and wrote a zero-sized widget back onto the item. load() re-applies gridstack's own defaults; onLayoutChange now reads a missing w/h as 1. - A drag followed immediately by navigating to another route detached the element inside the 150ms persist debounce, dropping the pending save. disconnectedCallback now flushes it to localStorage first. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ue9ZtWUBQF4SuSHpzZ3zwq