Datatable: Column Group Resizing Issue

[Saravananshankar98]

Describe the bug

This is the bug video: https://github.com/user-attachments/assets/6c0fd963-4836-4f01-acf4-51649f40767f

When using column grouping, I'm trying to resize a specific column, but the widths of the other columns are also changing, which is incorrect. The widths of the other columns should not be affected.

Additional Notes: The issue occurs specifically in the latest version 10.8.2. I have tried different configurations like switching between fit and expand modes, but the issue persists.

This is my code file: resizeColumnGroup.txt

Reproducer

https://stackblitz.com/edit/vitejs-vite-ym6tk5?file=src%2FApp.tsx.

System Information

"primereact": "^10.8.2", "react": "^18.3.1", "typescript": "^4.9.5", Environment: Windows 10

Steps to reproduce the behavior

No response

Expected behavior

No response

[github-actions[bot]]

Please fork the Stackblitz project and create a case demonstrating your bug report. This issue will be closed if no activities in 20 days.

[Saravananshankar98]

I have completed the code and created a case demonstrating the issue. You can review the details in my forked Stackblitz project here: https://stackblitz.com/edit/vitejs-vite-ym6tk5?file=src%2FApp.tsx.

Issue Description: When using column grouping, resizing a specific column incorrectly affects the widths of other columns, which should remain unaffected. The widths of other columns should not change when resizing one column.

Please take a look at the provided example to see the issue in action. If you need any additional information or clarification, feel free to reach out.

Thank you for your attention to this matter!

[melloware]

Thanks I updated the title and marked it a bug.

[melloware]

@KirilCycle another one to investigate? Said it used to work and now doesn't in 10.8.2?

[KirilCycle]

@KirilCycle another one to investigate? Said it used to work and now doesn't in 10.8.2?

Hi! I can't, I'm a bit busy.

[github-actions[bot]]

This issue has been automatically marked as stale. If this issue is still affecting you with the latest version, please leave any comment, and we will keep it open. We are sorry that we have not been able to prioritize it yet. If you have any new additional information, please include it with your comment!

[github-actions[bot]]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you for your understanding!