Fiori Elements routing as nested component - not tracking history correctly

[carlodevil]

OpenUI5 version: 1.120.13

Steps to reproduce the problem:

1. Create a ComponentContainer control in a freestyle UI5 app view.
2. Create a Fiori Elements app with more than one view (on different routes), with navigation between the views.
3. Load the Elements App as a nested control in the parent UI5 app.
4. In the nested elements app, programmatically navigate to the different route/view.
5. Click the browser back button to return to the previous view.

What is the expected result? The browser should return to the last history of the elements UI5 app.

What happens instead? The browser returns to the last history of the parent UI5 app, not the nested elements app.

Any other information? (attach screenshot if possible): It seems as if the child router doesn't notify the parent router of the Hash/Route change.

I have picked up this issue on one or two threads - will attach the links when I find it again.

[boghyon]

Is the Fiori elements app running in FLP? IIRC, there were a couple of issues with the back navigation within FLP. Unfortunately, neither the FLP nor the Fiori elements topic is part of this OpenUI5 repo.

Unless the same issue can be reproduced with a minimal OpenUI5 app alone, you'd have to create a customer ticket instead.

[carlodevil]

Noted, thanks @boghyon