[Bug]: Horizontal Scroll Bar in Table Widget Gone

[sjr267]

Is there an existing issue for this?

• I have searched the existing issues

Description

I have a table widget with more columns than will fit across the screen at once. In the past, there was a horizontal scroll bar at the bottom of the table that could be used to move the view to these columns, but this disappeared after yesterday's update. The only way I've found to scroll to these invisible columns is with the center wheel/button of the mouse.

Steps To Reproduce

In the editor, I can only get the horizontal scroll bar to appear in the table widget for a wide table if the table is the height of an integer number of rows. When I turn on cell wrapping and the rows become different heights based on the content, the horizontal scroll bar disappears because the table is no longer the height of an integer number of rows.

Public Sample App

No response

Environment

Production

Severity

Medium (Frustrating UX)

Issue video log

https://www.loom.com/share/4d80b47b1fd645ed80a7a8afe355aaee?sid=3a2c1df5-e647-4805-b952-e1029a570867

Version

Self hosted CE v1.25

[bejenaru]

on Cloud same issue

[sjr267]

Just discovered that this issue affects the vertical scroll bars as well. https://www.loom.com/share/5772acb273634974ac2a610f17c4233a?sid=ca1a14b4-07e0-49f7-ac05-5867d24c5032

[ame-appsmith]

Another user reported this bug.

[bejenaru]

I think the bug rise when the vertical bar is not showing.
In this case i have lots of rows and vertical bar is active resulting the horizontal one to be active also.

in this other case the table has only one row so the Vertical is not active. Nor the horizontal is active evenhough the table has more columns

[Nikhil-Nandagopal]

@bejenaru @sjr267 we have a preview of the fix here
https://ce-33806.dp.appsmith.com

Can you try it out and let us know if it solves the problem? You will need to create a new account on the URL I shared as it's a completely separate instance

[bejenaru]

Hi @Nikhil-Nandagopal
It is working ok on this instance!

[Nikhil-Nandagopal]

@bejenaru glad to hear it, the fix should be merged in soon