We can go to the next dialog when chaining dialogs and the related item doesn't have to be saved into JCR yet. This results into two problems:

1. The content change event is triggered after closing each dialog.
2. The tree is trying to select the item which doesn't exist yet. This results in a bug when adding a node at the root level since it tries to expand JCR root node (instead of the child which isn't saved yet) which is not part of the container.

Found after integration of PAGES-61.