[MGNLUI-4117] Loosing part or whole view port in tree view of page app Created: 11/Jan/17  Updated: 08/Mar/21  Resolved: 08/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: pages app, tree/list
Affects Version/s: 5.4.4, 5.4.10, 5.5
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Viet Nguyen Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows + MacOSX
JDK 8
Chrome + Firefox


Attachments: PNG File Screen Shot 2017-01-11 at 4.33.25 PM.png     PNG File Screen Shot 2017-01-11 at 4.56.14 PM.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 browsing and editing pages using Magnolia page app, user / we encountered a minor issue with tree view that need us to scroll down to update its UI.
Steps to reproduce, in some browsers you need to do it a bit quicker, sometimes it worked, sometimes it didn't:
Open page app then open 2 or more pages for editing.
Switch to page 1 tab, then close it, we will be redirected to tree view.
Switch to page 2 tab, then close it, you will see that we lost part or whole of the tree view as below image.
Scroll your mouse so that view port get updated and the tree display correctly again.

We can even right click on the remaining part of the page and the view port response with proper context menu, but right click on the missing part didn't get any response.



 Comments   
Comment by Roman Kovařík [ 08/Mar/21 ]

Closing as M5.5 has reached EOL and no support ticket is linked.
https://docs.magnolia-cms.com/product-docs/Support/End-of-life-policy.html#_end_of_life

Generated at Mon Feb 12 09:13:26 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.