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

Tree: Expanding a node scrolls to incorrect position when using Virtual Scroll #15336

Closed
LennartMart opened this issue Apr 22, 2024 · 1 comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@LennartMart
Copy link

Describe the bug

When using VirtualScroller, expanding a node scrolls to the wrong position in the tree. It's also broken on the documentation page: https://primeng.org/tree#preload .

Environment

17.14.1

Reproducer

https://stackblitz.com/edit/2uz5xq?file=package.json

Angular version

17.3.1

PrimeNG version

17.4.1

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

18.18.0

Browser(s)

No response

Steps to reproduce the behavior

  1. Scroll down in the tree
  2. Choose a node that wasn't initially visible
  3. Expand the node
  4. The tree will scroll upwards, the expanded node is out of sight.

Expected behavior

The expanded node should stay visible.

@LennartMart LennartMart added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Apr 22, 2024
@LennartMart LennartMart changed the title Tree: Expanding node scrolls to incorrect position when using Virtual Scroll Tree: Expanding a node scrolls to incorrect position when using Virtual Scroll Apr 22, 2024
@mertsincan
Copy link
Member

Hi,

So sorry for the delayed response! Improvements have been made to many components recently, both in terms of performance and enhancement. Therefore, this improvement may have been developed in another issue ticket without realizing it. You can check this in the documentation. If there is no improvement on this, can you open a new issue so we can include it in our roadmap?

Thanks a lot for your understanding!
Best Regards,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Projects
None yet
Development

No branches or pull requests

2 participants