Skip to content

[CFI] Allow table columns to be manually resized on web/desktop #101331

Open

Description

@shawnborton

We frequently get feedback from customers that they want to be able to fully customize the widths of columns shown on tables throughout the app. Let's create a system that allows for drag handles to be used to adjust columns widths.

First, we need to investigate if this is even possible. Note that we basically have two table systems:

  • Everything on the Spend page, which is quite custom
  • Every other table, which is standardized on our table component

Let's investigate if we can create adjustable columns first. In the meantime we'll come up with a few design ideas for how to display the handles.

cc @Expensify/design @JmillsExpensify

Issue OwnerCurrent Issue Owner: @Krishna2323

Activity

  1. war-in commented on Sep 16, 2026

    @war-in
    Contributor

    Hi, thank you for the assignment! As discussed here - https://expensify.slack.com/archives/C05LX9D6E07/p1789471962986829, I'll start the investigation

  2. war-in commented on Sep 16, 2026

    @war-in
    Contributor

    I implemented a very rough POC and already have a couple of questions 😄

    1. Sometimes the splitter is very hard to find, especially between rows that have no headers (Role and right arrow). How could we make sure users can find it? Maybe there could be a little indicator in the header row?
    2. What should be a minimal width of the column?
    3. What should happen with the Filters and Display pills when the table changes its width? Should they follow the right edge, or maybe stay in the default position?
    4. Should the user be able to shrink the table to the left, or should the right side always stick to the screen edge?
    5. Should the columns without a header even have a splitter? Should right arrow even be considered as a separate column?

    Here's a video for reference

    Screen.Recording.2026-09-16.at.18.32.26.mov
  3. JS00001 commented on Sep 16, 2026

    @JS00001
    Contributor

    cc @Expensify/design ^

  4. dannymcclain commented on Sep 16, 2026

    @dannymcclain
    Contributor

    Sometimes the splitter is very hard to find, especially between rows that have no headers (Role and right arrow). How could we make sure users can find it? Maybe there could be a little indicator in the header row?

    Design team can noodle about this one more but my first reaction is yeah maybe we could display something on hover? Maybe we could even highlight the header column that's being changed somehow? Not sure. We'll need to explore that a bit I bet. I do like the green line you're using so far though.

    What should be a minimal width of the column?

    Good question, I'm thinking something small but reasonable-ish... Maybe like 40px? 80px? Definitely curious for others' thoughts here.

    What should happen with the Filters and Display pills when the table changes its width? Should they follow the right edge, or maybe stay in the default position?

    I think they should stay put. Basically I think those control buttons as well as the search input and exposed filter pills should just behave like they're totally separate from the table and just stay as they are.

    Should the user be able to shrink the table to the left, or should the right side always stick to the screen edge?

    Slightly torn on this one but leaning towards letting them shrink it. Especially if we keep the filters/actions in place. I don't see a compelling reason to force the table to be full screen. 🤷

    Should the columns without a header even have a splitter? Should right arrow even be considered as a separate column?

    I don't think so. I do not think the arrow should be considered a separate column (so no resizing that one) and I'm tempted to even say the checkbox column and receipt/avatar/card columns should just be a fixed width. I think all the other columns have an actual header label and variable data (so it makes sense to be able to change the size of them). Open to pushback on that opinion though.

    P.S. This is VERY exciting 😁

    P.P.S. Dig the double-click to reset interaction it looks like you have going on ❤️

  5. shawnborton commented on Sep 16, 2026

    @shawnborton
    ContributorAuthor

    Super exciting!

    I don't see a compelling reason to force the table to be full screen. 🤷

    I think I disagree with this one - I don't think we should allow the table itself to be shrunk. Just allow resizing of columns, and if columns become too wide, we might force the table to become a horizontally scrollable table. I think AG Grid does this really cleanly.

    Should right arrow even be considered as a separate column?

    Totally agree, this column should not be able to be resized, so that means the column directly to the left of the arrow column should only be able to be resized from its left edge and not its right edge.

    Can we try those feedbacks first (both from Danny and myself) and then we'll address the visibility of the drag handle? It might be less bad once we fix some of the arrow column weirdness.

  6. dubielzyk-expensify commented on Sep 17, 2026

    @dubielzyk-expensify
    Contributor

    I think I disagree with this one - I don't think we should allow the table itself to be shrunk. Just allow resizing of columns, and if columns become too wide, we might force the table to become a horizontally scrollable table. I think AG Grid does this really cleanly.

    Agree.

    Excited to see where this goes.

  7. war-in commented on Sep 17, 2026

    @war-in
    Contributor

    Thanks for the detailed feedback! I made the table take up the entire screen width, but I encountered another issue.
    Which column should grow when I resize? If we always want the table to be at least as wide as the screen, we need to grow one column when shrinking another.

    E.g. grow the last one

    Screen.Recording.2026-09-17.at.12.58.04.mov

    AG Grid grows/shrinks all to the right

    Screen.Recording.2026-09-17.at.13.03.23.mov

    Slack doesn't have that issue because they let the table be smaller than the screen width


    We could also grow the first one to the right

    Screen.Recording.2026-09-17.at.13.14.56.mov

    Let me know which one feels best for you 🙏
    cc @shawnborton @dannymcclain @dubielzyk-expensify

  8. shawnborton commented on Sep 17, 2026

    @shawnborton
    ContributorAuthor

    AG Grid grows/shrinks all to the right

    This is what I would expect if none of those columns had been resized yet. If they hadn't been resized or don't have a custom width, they all should take up space equally.

  9. war-in commented on Sep 17, 2026

    @war-in
    Contributor

    And another one 😅

    I think they should stay put. Basically I think those control buttons as well as the search input and exposed filter pills should just behave like they're totally separate from the table and just stay as they are.

    If we want to pin the pills to the screen, we will have to remove them from the horizontal scroll. Because if we don't, the scroll will fight the sticky position, which just looks poor

    Screen.Recording.2026-09-17.at.13.51.01.mov

    On the other hand, it works really well on the Spend tab, where the search and pills are always pinned to the top of the page. However, this approach will break the current scroll-to-hide feature on the other tables (e.g. workspaces).

    @JS00001 @Krishna2323 have you encountered this problem while developing tables? Do you have any idea how to adjust the layout/implement it so we have non-scrollable content (search and pills) in a horizontally scrollable view?

    @shawnborton how do you feel about the two?

    1. Blocking the pills' position inside the horizontally scrollable view (elements slightly moving while scrolling)
    2. Making the pills & search always visible like on the Spend tab?
  10. shawnborton commented on Sep 17, 2026

    @shawnborton
    ContributorAuthor

    Sorry to report that I think we need to:

    • make sure the input/pills/buttons above the table always stay 100% width of the viewport
    • maintain our fixed header on scroll feature

    Sounds like quite the challenge! Is it possible?

  11. war-in commented on Sep 17, 2026

    @war-in
    Contributor

    @shawnborton fixed header shouldn't be a problem 😄 The actual problematic elements are the ones in the "page header" (input/pills/buttons). On the spend tab, they're always visible

    Image

    but other tables hide them on scroll

    Image Image

    I guess we need to preserve that behaviour, but let's confirm to stay aligned.

    And yeah, it is possible, but as you can see in the video from my previous message, they move a bit when scrolling (at least until I find a better solution)

  12. 123 remaining items

  13. melvin-bot commented on Nov 4, 2026

    @melvin-bot

    @Krishna2323 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

  14. melvin-bot commented on Nov 4, 2026

    @melvin-bot

    @Krishna2323 Still overdue 6 days?! Let's take care of this!

  15. melvin-bot commented on Nov 11, 2026

    @melvin-bot

    @Krishna2323

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.35-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

ReviewingHas a PR in reviewSkip PaymentSkips all the payment process steps for an issue. Use it for fixed-price projects.WeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions