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

Table: rowspan issue when the table is frozen and scrollable #15362

Closed
alisesan opened this issue Apr 25, 2024 · 1 comment
Closed

Table: rowspan issue when the table is frozen and scrollable #15362

alisesan opened this issue Apr 25, 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

@alisesan
Copy link

alisesan commented Apr 25, 2024

Describe the bug

Describe the bug
There is an issue with the rowspan attribute when the table is scrollable and frozen. The horizontal scroll breaks the layout for the forzen columns.

After debug it seems that the rowspan is ignored and the calculation of the left property is wrong for the second line

Environment

image

Reproducer

https://stackblitz.com/edit/primeng-tableselection-demo-712q71?file=src%2Fapp%2Fapp.component.html

Angular version

13.0.3

PrimeNG version

13

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

16.10.0

Browser(s)

Chrome

Steps to reproduce the behavior

Use the horizontal scroll. The second line of the header will ignore the rowspan and overflow the cell

Expected behavior

The second line of the header should take the rowpan in consideration

@alisesan alisesan 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 25, 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