[MGNLFE-215] Race condition when calling "onFrameReady" and "refresh" Created: 13/Jun/22  Updated: 29/Nov/22

Status: Open
Project: Magnolia Frontend Helpers
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Bartosz Staryga Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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: SPA Editor Backlog

 Description   

Currently, couple of context functions tell Magnolia to draw green bars:

  • onFrameReady
  • refresh

are called on editable page level only.
In some cases component is rendered way later after the page update, resulting in not all components having green bars rendered.

Can we please call both methods also on the editable component update life cycle method too?



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

bstaryga When you say "In some cases component is rendered way later after the page update" - is this what you mean by race condition? Or ... how much later do you mean - like in response to a user taking some action on the page? Or do you still just talk aabout slowish rendering.

I think the race condition issue taht I know of is being addressed in ..
https://jira.magnolia-cms.com/browse/MGNLFE-208 / 
https://jira.magnolia-cms.com/browse/MGNLFE-37

Do you think that addresses your issue - or do you think you have a different issue?

Comment by Bartosz Staryga [ 13/Jun/22 ]

208 if implemented in a way that method is called on editable component update then yes, so depends on the 208 implementation

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