[MGNLUI-2170] New Pulse messages might not get updated in time (display as 'null') Created: 25/Sep/13  Updated: 09/Mar/21  Resolved: 09/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: testing
Affects Version/s: 5.0.4, 5.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Philip Mundt Assignee: Aleksandr Pchelintcev
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File FavoriteUITest.png    
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:

 Description   

When sending a message to the pulse in tests and opening the message overview afterwards, messages might show as 'null', and thus are not in the correct order (date is 'null' too).

To workaround one has to reopen pulse. After that, the messages appear correctly.



 Comments   
Comment by Aleksandr Pchelintcev [ 26/Sep/13 ]

Due to the constant presence of the shell apps in the DOM tree we have to maintain their connectors. The complex thing is that as long as at least two shell apps are hidden (CSS display:none) Vaadin does not update them fully. Thus, when Pulse is hidden and we add a message to it, the server notifies the client, but actual rendering does not happen. When we open up Pulse - it first finishes the rendering phase (and would show a row/rows with empty/null cells) and trigger server to send updates again, so for a split second we see incorrect values for some rows.

Comment by Daniel Lipp [ 30/Sep/13 ]

Recorded by UITest execution

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