Scrollbar Extending Beyond Table Body in PrimeNG p-table Component

[vbnr]

Describe the bug

In the provided example from the PrimeNG p-table documentation, the scrollbar extends beyond the table body, appearing in area such as the table heading.

Environment

• Angular version: 16.0.3
• PrimeNG version: 16.0.2
• Node version: 18.13.0
• Browser: Chrome 121.0.6167.185
• Windows 11

Reproducer

No response

Angular version

16.0.3

PrimeNG version

16.0.2

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

18.13.0

Browser(s)

Chrome 121.0.6167.185

Steps to reproduce the behavior

1. Visit the PrimeNG p-table documentation, Section Scroll/Vertical Scroll
2. Review the example demonstrating a table with a predefined scrollHeight making the header section sticky.

Snippet of the example:
<p-table [value]="customers" [scrollable]="true" scrollHeight="400px" [tableStyle]="{'min-width': '50rem'}">

Screenshot:

Expected behavior

The scrollbar should be within the body of the table and should not extend beyond it. The header section should remain sticky as the user scrolls through the table content.

[vsawant18]

I am also facing the same issue. Suddenly from the last 3 days, table column has not obeyed its width and taken size as the max length of text in that column and showing a horizontal scrollbar at the bottom. Please find the below screenshot.

Angular: 14.1.0
primeng: 14.2.3
https://registry.npmjs.org/primeng/-/primeng-14.2.3.tgz

[robGardiner01]

I made a start on this and found that it can be fixed by altering the CSS of the table's head and body to "display: block" and setting a specific height for the body. However, this means the head and body columns do not line up unless their widths are explicitly set.

[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!