Table: Grouped header + horizontal scrolling body has regressed from pre v12.1.0

[Phil-DS]

Describe the bug

Scrolling (Mainly horizontal)+grouped header leads to extremely broken layouts

Environment

Been migrating from Angular 11 to angular 14, and the changes in #10495 for 12.1.0 has been detrimental to a fair few table layouts in my use case that worked previously. The issue here stems from the combination of a grouped/spanned header with horizontal scrolling (There are more columns that needed to be fitted on to the side). Without colgroup to keep things structured, it's a mess trying to keep things in line. If there is no width fixing, then the entire table squashes down, preventing horizontal scrolling. When trying to add some width to try fix the issues, the header and the body require 2 completely different methods to even try to fix the widths. Then, after all of that, they still don't stay in place.

I originally thought this was a part of #11715, but it's a bit more than that. Header grouping+scrolling is just a regression of functionality. The changes may have been useful elsewhere, but it has come at the expense of breaking existing features.

Reproducer

https://stackblitz.com/edit/table-groupedcol-scroll-issues

Angular version

14.1.0

PrimeNG version

14.1.1

Build / Runtime

TypeScript

Language

TypeScript

Node version (for AoT issues node --version)

16.13.0

Browser(s)

Chrome

Steps to reproduce the behavior

Add scrolling (Both directions) and grouped headers to the table.
See the results.

Scroll to the right of the table in the stackblitz

The second one tries to handle some fixed widths

Toggle scrolling on and off to see the difference.

Expected behavior

The columns should be able to line up correctly and responsively.

[Phil-DS]

Going to check this out with the major changes from v14.2.0

[Phil-DS]

Will check more, but the update seems to fix this issue!

[github-actions]

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]

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!