[ADMINCTR-420] Make subapp closing behaviour configurable Created: 03/Jul/23  Updated: 03/Jul/23

Status: Open
Project: Admincentral
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Adam Siska Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
causality
caused by ADMINCTR-408 Close action should work the same way... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
ADMINCTR-421 Implementation Sub-task To Do  
ADMINCTR-422 Review Sub-task To Do  
ADMINCTR-423 Pre-Integration QA Sub-task To Do  
ADMINCTR-424 QA Sub-task To Do  
Template:
Acceptance criteria:
Empty

 Description   

During the work on ADMINCTR-408 we realize that expected behaviour after closing subapp either by closing button (in tab) or by closing with cancel/commit action could be different.

We fixed the issue (for Groovy app especially) by unifying closing behaviour with x-button closing, i.e. returning always to browser subapp. This solution won't affect e.g. Pages app (there is no closing action in page editor) but changes behaviour for content-type apps.

There are possible solutions described in this task ADMINCTR-413 but the ultimate solution would be apparently making it configurable as mention here: https://jira.magnolia-cms.com/browse/SUPPORT-15515?focusedId=326423&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-326423
(or revert the fix done in ADMINCTR-408 and refactor the Groovy app, also mentioned in linked comment)


Generated at Sun Feb 11 23:06:57 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.