[MGNLFE-37] mgnlRefresh is not available when the PageEditor first loads Created: 21/Apr/20  Updated: 03/Aug/22  Resolved: 22/Jun/22

Status: Closed
Project: Magnolia Frontend Helpers
Component/s: None
Affects Version/s: 1.0.0, 1.2.2
Fix Version/s: 1.2.2

Type: Bug Priority: Major
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: cs-bk
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Relates
relates to MGNLFE-26 inEditor context incorrect if mgnlRef... Closed
relates to MGNLFE-208 Greenbars sometimes not appearing on ... 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:
Epic Link: Support
Story Points: 0
Team: DeveloperX

 Description   

The SPA app can load faster then the mgnlRefresh is added to the window, this will cause bugs if the app tries to use mgnlRefresh - but mgnlRefresh is not available yet. Namely, the green bars won't get rendered.

In practice, this problem won't occur that often because the SPA app will be also be making a call to the REST endpoints to load content before calling mgnlRefresh. But it can happen if the REST response is faster then the mgnlRefresh being added. 

Or a developer might have hardcoded some json fragments and might not make a REST call during some testing for example.



 Comments   
Comment by Christopher Zimmermann [ 22/Jun/22 ]

Fixed in linked ticket: https://jira.magnolia-cms.com/browse/MGNLFE-208

Generated at Mon Feb 12 05:43:37 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.