Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem: Full-width treeview not always focusing on current description. #1825

Open
melaniekung opened this issue Jun 12, 2024 · 1 comment
Labels
Type: bug A flaw in the code that causes the software to produce an incorrect or unexpected result.

Comments

@melaniekung
Copy link
Contributor

melaniekung commented Jun 12, 2024

Current Behavior

Sometimes, opening a record/material of a large repository/series does not focusm set the focus of the full-width treeview on the current record/material.

Expected Behavior

Regardless of the size of repository/series, when you open a record/material, the treeview should always focus on the current record/matieral.

@melaniekung melaniekung added the Type: bug A flaw in the code that causes the software to produce an incorrect or unexpected result. label Jun 12, 2024
@fiver-watson
Copy link
Contributor

@melaniekung if you are seeing this in older installations it may already be solved by #1748 - typically when we see this behavior in the past, it was due to a child record being outside the initial paging value set for the full-width treeview. PR #1757 increased the default installation value to 8000 which should most issues (if this is in fact the cause) save for the largest of hierarchies - however, I don't know if there was a migration script for upgrading users, and even if there was, I doubt it would modify the existing value if a user had already modified it themselves.

Therefore, for any existing installation where this behavior is seen, my first suggestion would be to check the treeview pager value and try increasing it, restarting services / possibly reindexing, and then see if you can reproduce the problem.

If yes: then it's likely something else. If no, then it may be a solved issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: bug A flaw in the code that causes the software to produce an incorrect or unexpected result.
Projects
None yet
Development

No branches or pull requests

2 participants