[MGNLUI-2262] Order of the tabs can be altered by opening a sub app using its URL Created: 09/Oct/13  Updated: 09/Mar/21  Resolved: 09/Mar/21

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

Type: Bug Priority: Major
Reporter: Christoph Meier Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: next, ux
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File 1 Switch to Roles tab+copy URL.png     PNG File 2 Close app+paste URL.png     PNG File 3 Roles tab is now 2nd.png    
Issue Links:
duplicate
is duplicated by MGNLUI-1899 Security app tabs move around Closed
relation
is related to MGNLUI-2908 BaseSubApp does not restore the corre... Closed
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
Date of First Response:

 Description   

The order of sub-apps (order of the tabs) can be changed by URI or favorite, if the app was not open before.

To reproduce

  • make a favorite for the sub-app "roles", which is usually shown on last position (4th), if you just open the security-app.
  • close the sec.-app and call the sub-app "roles" with the favorite-link.
    => now "roles" will be on the 2nd place.

Every time when an app is closed and you call a sub-app with a location-link, the subapp of the location-link will be rendered always on the 2nd place (if its not the 1st by definition)



 Comments   
Comment by Andreas Weder [ 04/Sep/15 ]

Sub apps seem to always open in the 2nd tab, if opened using a URL. So this is somewhat "by design". But this collides with apps that have a fixed set of open tabs. In such a case, that order should be respected.

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