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: Primeng table with expanded rows and frozen columns (which are represented as table) #14711

Closed
imotality opened this issue Feb 5, 2024 · 3 comments
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@imotality
Copy link

Describe the bug

While describing primeng table and using expandable table with frozen column, I represented the expanded rows as another p-table. I have added for both of them frozen columns, but when I want to scroll, positioning are wrong, and it only scrolls parent table. I want to connect 2 tables as one to have the same scroll. How can i do that?

Environment

using primeng v.15

Reproducer

No response

Angular version

15

PrimeNG version

15

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

18

Browser(s)

No response

Steps to reproduce the behavior

create p-table with frozen columns, and after create expanded rows as representing of another p-table with frozen column and try to scroll it vertically.

Expected behavior

both tables with frozen columns are syncronized

@imotality imotality added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Feb 5, 2024
@imotality
Copy link
Author

imotality commented Feb 5, 2024

image

the example while scrolling

@mehmetcetin01140
Copy link
Contributor

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