[MGNLUI-2669] Make sure applauncher collapsible groups always open on top of permanent groups Created: 11/Feb/14  Updated: 06/May/14  Resolved: 11/Feb/14

Status: Closed
Project: Magnolia UI
Component/s: applauncher
Affects Version/s: 5.2.2
Fix Version/s: 5.2.3

Type: Bug Priority: Neutral
Reporter: Mikaël Geljić Assignee: Mikaël Geljić
Resolution: Fixed Votes: 0
Labels: quickwin
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File applauncher-tempgroup-above.png     PNG File applauncher-tempgroup-behind.png    
Issue Links:
duplicate
is duplicated by MGNLUI-2731 If a group is opened, its app icons a... 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

 Description   

If a permanent group is declared last in appLauncherLayout (as when an extra module brings a whole new app group), then collapsible groups expand below this app group if screen estate is too small.

See applauncher-tempgroup-behind.png, STK group wrongly expands below Data group (used as permanent for the example).

This is because app groups will be appended to DOM in same order as in config.

Order on the client should ensure all collapsible groups are appended last, so that modules which bring new permanent group don't have to use OrderNode*Tasks as extra install tasks.


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