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

TreeTable ttResizableColumn broken in both expand and fit mode with nothing special added into the mix #15180

Closed
ILIA-BROUDNO opened this issue Mar 27, 2024 · 1 comment
Assignees
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working

Comments

@ILIA-BROUDNO
Copy link

ILIA-BROUDNO commented Mar 27, 2024

Describe the bug

A working TreeTable with normal (non virtual) vertical scroll and dynamic columns breaks when I add ttResizableColumn to <th and [resizableColumns] = 'true' in <p-treeTable

Dragging the splitter moves the blue vertical line, but releasing the left mouse button never releases the line so it just keeps moving around with the mouse and column sizes do not change.
See here for repro:
https://stackblitz.com/edit/jch81r-jxqwvh?file=src%2Fapp%2Fdemo%2Ftree-table-selection-checkbox-demo.html
It's based on Primeng's own demo project with only added resizable columns

Environment

Primeng versions 15.4.1 and 17.11.0 (may be more)
VS Code on Windows 10 hosting the app with Node.js v18.13.0
Browser is Chrome v121.0.6167.87 incognito mode; MS Edge v123.0.2420.53 ; Firefox v123

Reproducer

https://stackblitz.com/edit/jch81r-jxqwvh?file=src%2Fapp%2Fdemo%2Ftree-table-selection-checkbox-demo.html

Angular version

15.2.6

PrimeNG version

15.4.1 and 17.11.0 (may be more)

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

18.13

Browser(s)

Chrome v121.0.6167.87 incognito mode; MS Edge v123.0.2420.53 ; Firefox v123

Steps to reproduce the behavior

open see repro project on stackblitz and try resizing columns

Expected behavior

they should resize :) , but they don't

@ILIA-BROUDNO ILIA-BROUDNO added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Mar 27, 2024
@mehmetcetin01140 mehmetcetin01140 added Type: Bug Issue contains a bug related to a specific component. Something about the component is not working and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels May 15, 2024
@mehmetcetin01140 mehmetcetin01140 added this to the 17.16.3 milestone May 15, 2024
@cetincakiroglu cetincakiroglu modified the milestones: 17.18.0, 18.Future May 30, 2024
@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,

@github-project-automation github-project-automation bot moved this to Done in PrimeNG Dec 16, 2024
@mehmetcetin01140 mehmetcetin01140 removed this from the 19.x milestone Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
Status: Done
Development

No branches or pull requests

3 participants