Node creation event outside of container bounds forces its resize

[RaphaelPageObeo]

• I have checked that this bug has not yet been reported by someone else
• I have checked that this bug appears on Chrome
• I have specified the version :

• latest

• I have specified my environment :

• my computer: Windows

Screenshots

Steps to reproduce

• I have two root nodes, A { size: 200x300, position: 10;10 } (in blue) and B { size: 200x300, position: 500;500} (in orange)
• I click on (100;100) (inside A, red dot) and send a creation event
• The editing context actually creates the new node in B

Expected behavior

• A { size: 200x300, position: 10;10 }
• B { size: 200x300, position: 500;500 }
• Child { size: 150x70, position: 510;510 }

A is not resized. B is not resized either, since it is big enough to contain the new node. The new node is created in B, since it is a son of B.

Actual behavior

• A { size: 200x300, position: 10;10 }
• B { size: 600x700, position: 231;231 }
• Child { size: 150x70, position: 231;231 }

A is not resized. The new node is created in B...but not at the right coordinates, which forces B to be resized

[gcoutable]

I don't understand why the click inside A creates a child in B.
Does the child already exist in the model and it is a child of B?

[sbegaudeau]

Yes, it's to simulate an operation triggered by a tool on A which creates a child in B. I think I won't surprise you by saying that it was my idea :p

I wanted to challenge a bit our expectation and see how our code would react.