router.push keeps all views attached

Hello there!

I have an issue where router.push just stacks views on top of each other and you even can click through the views.

Not sure if it is desired behavior, but I expected it to work similar to fragment manager: when you push, current view gets detached and new view is attached. When you press “Back”, previous view gets attached with restored state.

Here is the repo to reproduce: https://github.com/timopl/ribs-push

Thanks!

[zsoltk]

@Gaket Yes, if it’s the same back stack. Look at it from the parent’s perspective. The parent has control over its own back stack and what things can go there - these are any other RIB that it can build (satisfying their dependencies) and it wants to build (matched to a Configuration).

Although the above does not mean that you always need to have everything that can cover the full screen nested under the same parent. That would result in one “super node” and wouldn’t be efficient. You have some other options:

1. any level in the tree can be just a container which adds nothing to the view directly (its ViewFactory is null), so its whole available screen space is given to its children.
2. you can use Portals to open something full screen even if the parent itself has access to a portion of the screen.

[zsoltk]

Also worth to mention you don’t need to channel your UI event through a Feature to produce a navigation event, that just adds lots of unnecessary steps with no extra benefit. You can bind ui event to router.push directly. Feature is best used for things that are related to changing state.