[MGNLUI-1799] Problems when entering location for app that does not exist Created: 28/Jun/13  Updated: 09/Mar/21  Resolved: 09/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: app framework, applauncher
Affects Version/s: 5.0
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Tobias Mattsson Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

There's two different problems that can be caused by entering a location such as http://localhost:8080/.magnolia/admincentral#app:doesnotexist

When there's no apps running and you enter a location for an app that does not exist this results in an empty green screen, at this point the shell icons respond either slowly, not at all, and sometimes they work but the shell apps appear left aligned.

When there's an app running,
entering a location with an app that does not exist makes LocationHistoryHandler fall back to default location which is shell:applauncher. Entering it a second time removes app launcher and leaves the faulty app name in the location bar. What happens on the server side is that LocationController decides against this location and wants to go to the default location, but it knows that its already there so it does nothing. The problem with the disappearing applauncher is likely on the client side. LocationController though, should probably set the fragment even when it decides to stay where it is.


Generated at Mon Feb 12 08:50:15 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.