Stunner - Adding an element from the palette, as a child of multiple parents, results in the element added in the wrong coordinates

Consider having two nested container shapes, once adding a new element from the palette, the new shape is being added in the wrong location.
See attached screenshot as example - the mouse pointer specifies the drop target, but the new shape (task) has been added into the wrong location.

test scenario: Subprocess within a lane — dragging a start node from the palette