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. Resizable columns with column grouping #15844

Closed
dperezfadonminsait opened this issue Jun 14, 2024 · 1 comment
Closed

Component: Table. Resizable columns with column grouping #15844

dperezfadonminsait opened this issue Jun 14, 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

@dperezfadonminsait
Copy link

dperezfadonminsait commented Jun 14, 2024

Describe the bug

When using grouped Columns with resizableColumns the resize functionality fails.

example: https://stackblitz.com/edit/6cvsqv?file=src%2Fapp%2Ftable-column-group-demo.html

Environment

Primeng 17, Angular 18

Reproducer

https://stackblitz.com/edit/6cvsqv?file=src%2Fapp%2Ftable-column-group-demo.html

Angular version

18.0.1

PrimeNG version

17.18.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

17.18.0

Browser(s)

Chrome

Steps to reproduce the behavior

Resize in table headers, first works, with the others weird things happens.
Without colspan > 1 in tds of the header everything goes ok.

Expected behavior

Everything resizes with no problems.

@dperezfadonminsait dperezfadonminsait added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Jun 14, 2024
@dperezfadonminsait dperezfadonminsait changed the title Component: Table Component: Table. Resizable columns with column grouping Jun 17, 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