[Bug] - Resizing the pool causes buggy editor

[Hafflgav]

Describe the bug
When I open a BPMN model in the VS Code Modeler and I want to resize the pool, the behaviour shown in the video occurs.
It can be forced by expanding the pool to the top. Sometimes though, it happens in any given direction.
It was a bit unfortunate to experience this behaviour during a live demo of our VS Code Modeler. 😢

To Reproduce
Steps to reproduce the behavior:

1. Open a BPMN file in the VS-Code Modeler
2. Resize the pool in any given direction
3. If it does not show the behaviour shown in the video redo step 2
4. See behaviour which is shown in the video

Expected behaviour
Resizing of a pool does not cause the Modeler to reset view point to a white canvas. Editing the size of the pool should be always possible

Screenshots
Video:

Desktop (please complete the following information):

• OS: macOS 13.5.2 (22G91)
• VS Code Version: 1.82.1
• Miranum Modeler: v0.5.3

[peterhnm]

The bug occurs because of this module.
It is described here

[Hafflgav]

Hey @peterhnm 👋
Thanks for the very fast fix of the problem 🚀
It doesn't crash anymore 👍

But besides, I have found another behaviour related to the viewport, which was a bit unexpected to me:

My expectation would be that the viewport does not change when placing a BPMN-Element on the modelling canvas.
This behaviour can especially be seen when moving only start event on the canvas.

Let me know what you think about this!

[peterhnm]

I like this behavior because it means less scrolling for me, for example after a resize of a pool.

What do you think about configuring it so that the user can turn this behavior on and off?

alignToOrigin.mov