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

Component: Table - Virtualscroll + Frozen cols broken when scrolling upwards #16581

Open
j4ckp0t85 opened this issue Oct 18, 2024 · 1 comment
Labels
Resolution: Help Wanted Issue or pull request requires extra help and feedback
Milestone

Comments

@j4ckp0t85
Copy link

Describe the bug

When using a table with virtualscroll feature and a bunch of frozen columns the vertical scrolling seems broken, especially going upwards.
On the interface you notice a rows jump effect caused probably by a wrong slice offset handled.
The onScrollIndexChange callback is emitting twice going upwards with two different indexes

Environment

Tried both on local environment and stackblitz

Reproducer

https://stackblitz.com/edit/es8wpw-ixccng

Angular version

17.3.12

PrimeNG version

17.18.11

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. Drag and drop the vertical scrollbar at a certain point (outside the pre-rendered items)
  2. Scroll upwards slowly

Expected behavior

It should respect the correct offset slice to be renderer on viewport / pre-rendered tolerated items

@j4ckp0t85 j4ckp0t85 added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Oct 18, 2024
@mertsincan mertsincan added Resolution: Help Wanted Issue or pull request requires extra help and feedback and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Nov 19, 2024
@mertsincan mertsincan added this to the Future milestone Nov 19, 2024
Copy link

Due to PrimeNG team's busy roadmap, this issue is available for anyone to work on. Make sure to reference this issue in your pull request. ✨ Thank you for your contribution! ✨

@github-project-automation github-project-automation bot moved this to Review in PrimeNG Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Help Wanted Issue or pull request requires extra help and feedback
Projects
Status: Review
Development

No branches or pull requests

2 participants