[MGNLUI-4743] Regression: Restore user-based location control Created: 29/Oct/18  Updated: 03/May/19  Resolved: 03/May/19

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.0
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Federico Grilli Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLUI-4652 IllegalArgumentException thrown by Fr... Closed
causality
is causing MGNLUI-4793 Find Bar: Suggestions are filtered by... Closed
duplicate
is duplicated by MGNLUI-4758 Find Bar filters results by an app th... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

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



 Comments   
Comment by Antti Hietala [ 09/Nov/18 ]

Unable to reproduce. Back/fwd button navigation seems to work.

Regardless, I guess we should restore `DefaultLocationHistoryMapper` anyway, in order to have a reliable. predictable history navigation within Magnolia.

Generated at Mon Feb 12 09:19:39 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.