-
Task
-
Resolution: Obsolete
-
Neutral
-
None
-
6.0
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
See DefaultLocationHistoryMapper: ideally without AppLauncherLayoutManager.getLayoutForUser
Reproduction:
- Go to pages app and navigate to stories app and press back button, it should navigate back to pages app.
Business benefit:
This is how modern Web applications should work: rather than prevent the user from clicking the Back and Forward buttons, let them do what feels intuitive. If clicking Back seems like the right thing to do to get to the previous state then the application should support that feeling. Using the URL fragment allows the user to use the browser’s own back and forward functionality.
– Docs: Moving back and forward in browser history
- is causing
-
MGNLUI-4793 Find Bar: Suggestions are filtered by app last visited
- Closed
- is duplicated by
-
MGNLUI-4758 Find Bar filters results by an app that was already closed
- Closed
- relates to
-
MGNLUI-4652 IllegalArgumentException thrown by Fragment being null or empty (Admincentral navigation)
- Closed