[MGNLUI-307] Browser reload of pages/contacts app shows both tree grid if the two apps are open Created: 03/Dec/12  Updated: 11/Feb/13  Resolved: 04/Dec/12

Status: Closed
Project: Magnolia UI
Component/s: app framework, user interaction
Affects Version/s: None
Fix Version/s: 5.0

Type: Bug Priority: Critical
Reporter: Philipp Bärfuss Assignee: Mikaël Geljić
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLUI-334 Simplify VShellViewport handling of a... 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:

 Description   
  1. open pages app
  2. open contacts app
  3. use browser reload
    --> the content of both the trees are shown


 Comments   
Comment by Mikaël Geljić [ 03/Dec/12 ]

Client-side viewports currently don't update server back on which widgets (apps) are currently displayed and which are hidden.

They should "updateVariables" when showing/hiding an app, both through setVisible(false) or getStyle().setVisibility(Visibility.HIDDEN).

Comment by Mikaël Geljić [ 04/Dec/12 ]

Or better; the server initially decides which app to display (DeckLayout#display() so a first fix consists of setting appropriate visibility on server-side in the first place.

Then when refreshing (without ?restartApplication of course), client-state is in sync again.

Finally, client-side logic should be reviewed to simply react to such visibility changes and nothing more. Currently all displaying/hiding logic of viewports is client-side only, hence the overlapping workbenches, since server considers both of them visible).

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