Border node can change position when moving the parent node

[mcharfadi]

It appears if the border node is placed at the bottom left after a resize and then a move is performed on the parent node.

20251219-0847-19.4687929.mp4

[cbrun]

Hi, is that the same issue ? The behavior I witness on this modeler (see the video) is a significant regression from a usability perspective.

2026-01-26.16-39-23.mp4

I would have expected the port to stay eactly where they are and not move erratically when biding them.

for the record: I'm using 2025.12.2 in this tooling.

[frouene]

Hi, is that the same issue ?

I don't think so, this behavior has been add related to this issue #5635
The problem with your scenario is that the edge creation, in addition to linking the two border nodes, creates another node with an edge on it.
We will thus move the border node from the left side to the right to rationalize the edge with this new node. But it creates a strange situation with the two existing border nodes.
I don't see a simple behavior that would satisfy all scenarios. Perhaps we could apply the automatic movement of the border node only in cases where they are connected by edges to other border nodes and not to classic nodes.

[cbrun]

Perhaps we could apply the automatic movement of the border node only in cases where they are connected by edges to other border nodes and not to classic nodes.

Indeed, in my case at least, the "smartness" leads to something more strange than what we had before. I would understand that if we would have "created the ports while creating the connection" then SW would try to place them smartly. But here the ports are already placed. I would not have expected them to move when connecting them explicitely.