[MGNLUI-6242] Scroll to selected item does not work after search or deeplink request Created: 24/Sep/20  Updated: 20/Aug/21  Resolved: 30/Nov/20

Status: Closed
Project: Magnolia UI
Component/s: content app
Affects Version/s: 6.2.3
Fix Version/s: 6.2.6

Type: Bug Priority: Major
Reporter: Frank Sommer Assignee: Roman Kovařík
Resolution: Fixed Votes: 1
Labels: 623
Remaining Estimate: Not Specified
Time Spent: 7h 47m
Original Estimate: Not Specified

Attachments: PNG File 1.png     PNG File 2.png     PNG File 3.png    
Issue Links:
Cloners
is cloned by MGNLUI-6430 Scroll to selected item does not work... Closed
Problem/Incident
Relates
relates to MGNLRES-358 Scroll to resource with browser link ... Closed
relates to MGNLTEST-101 UI Tests relying on visibility of Gri... Closed
relates to MGNLUI-6599 Scroll to selected item does not alwa... Closed
causality
is causing MGNLTEST-128 Investigate intermittent failures reg... Closed
is causing MGNLUI-6398 Remove grid scroll extension Closed
documentation
to be documented by MGNLUI-6434 DOC: New scrollToSelectedItem propert... Closed
duplicate
duplicates MGNLUI-3535 Lost viewport in content-views (ex. l... Closed
is duplicated by MGNLUI-5548 Grid on M.6-UI doesn't scroll to sele... Closed
is duplicated by MGNLUI-6290 New UI apps: Search result(findbar) a... Closed
relation
is related to MGNLUI-3675 Chooser dialog should remember last u... Closed
supersession
supersedes EXTDAM-185 [Bynder] Change sub-app button to 'Up... 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
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Epic Link: Scroll to selected item
Sprint: UI FW 14, UI FW 16
Story Points: 5

 Description   

If you search for an item on first level in a content app and click on the search result item, the opened content app doesn't scroll to the right position. The content app is still at the top and the user must scroll down.

You can reproduce this on demoauthor instance by adding many assets in the dam app on top level. If you search for it, the app doesn't scroll to the searched item.

Steps to reproduce

  • Search for something in the find bar, in the example we searched in demoauthor for "hanoi"
  • Click on the first result which takes you to the Assets app
  • This takes you to the content app where there are many assets already and you cannot see the asset you were looking for unless you scroll down:


     
    Expected results
    Once you search, you should only get the result you are looking for and should not have to scroll down. In the case of this customer they manage thousands of entries which makes it a big issue for them.
     
    Actual results
    You need to scroll down until you see what you are looking for

Notes
Works as expected in legacy apps on 6.2.3 (custom java script extending vaadin 7).
E.g. search for 'dolphins' on our demo, use result from 'Assets' (legacy app)
Or click this deep link:
https://demo.magnolia-cms.com/.magnolia/admincentral#app:assets;/stories-demo/found-in-switzerland/tours/flickr_dolphins_Tony-Malkevist-for-the-Israeli-Ministry-of-Tourism_15391214725_e6cdb14869_k.jpg:edit

-GridScrollExtension - does not lookup index, only allows scrolling to a point, we don't know what the position is.- This is supported by grid API itself, extension actually only remembers scroll position



 Comments   
Comment by Simon Lutz [ 28/Sep/20 ]

This is not yet implemented due to performance reasons. We may need to load the whole DB chunk-by-chunk in quest for the selected item. We may need to come up with a UX solution that workarounds this issue; e.g. show the searched & selected item on top or something along those lines.

FYI avongunten

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