[MGNLUI-1529] Overlay problems: transitions and architecture. Created: 03/Jun/13  Updated: 14/Jun/13  Resolved: 14/Jun/13

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

Type: Bug Priority: Critical
Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev
Resolution: Fixed 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

Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLUI-1536 The way overlays are closed is danger... Sub-task Closed Aleksandr Pchelintcev  
MGNLUI-1537 Three UIContext implementations are 1... Sub-task Closed Aleksandr Pchelintcev  
MGNLUI-1538 Overlay transitions are broken. Sub-task Closed Aleksandr Pchelintcev  
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
Sprint: Beta 3

 Description   

Instead of performing the transitioned close operation on the client-side overlays create a progress indicator and server-side Timer which causes warnings and unnecessary requests. We should consider moving that logic to the client-side.


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