After doing changes to an element in an editor window and saving them, the tree in the model browser is sometimes moved so that the parent of the saved item is aligned as the lowest visible element. The edited item itself is not visible in the view.
@tvavrda This behavior is intentional. Do we want to change it?
I think this was mainly important for the use case when e.g. a new entity is being created and the user wants to basically be parked on the entity while adding fields to it. Or maybe there was even another case but I cannot remember it.
So I think these are colliding use cases.
@tvavrda so should we close this issue?