You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The PR got merged and the fix was released in 17.1.something.
For some reason when looking at the master version of primeng the fix disappeared and also seems to be gone from the git history ?
As the PR was accepted and merged before already I did not create a reproducer. If I have to I can do it.
Was this intentional or an accidental force push or something? Can the PR be merged to master again? I can confirm the bug is still present in the current master version!
I think what happened is that the previous v18 branch was renamed to master, while the current master branch was renamed to v17. There was no merge from v18 to master.
You should reopen the PR. The PrimeNG will probably accept the PR again.
Describe the bug
Hi there, in November I submitted an issue and PR for a resizing bug in the table control.
This is the issue: #16734
The PR got merged and the fix was released in 17.1.something.
For some reason when looking at the master version of primeng the fix disappeared and also seems to be gone from the git history ?
As the PR was accepted and merged before already I did not create a reproducer. If I have to I can do it.
Was this intentional or an accidental force push or something? Can the PR be merged to master again? I can confirm the bug is still present in the current master version!
Thanks & best regards,
Janik
Pull Request Link
#17461
Reason for not contributing a PR
Other Reason
No response
Reproducer
#16734
Environment
windows 11, vscode, does it matter?
Angular version
19.0.0
PrimeNG version
v19
Node version
No response
Browser(s)
No response
Steps to reproduce the behavior
Create a table with sortable & resizable columns and try to resize a column. Exceptions will be thrown.
Expected behavior
No exceptions & resize works as expected
The text was updated successfully, but these errors were encountered: