Skip to content

Design: Responsive tables #2025

Open
Open

Description

@benjaminleonard
No description provided.

Activity

  1. benjaminleonard commented on Mar 6, 2024

    @benjaminleonard
    ContributorAuthor

    Exploring the feasibility of something like this for mobile:

    image.png

    The idea being we take the first cell (assuming that's the primary one). We drop the more actions menu in there and hide it on larger screens. We can then add an optional flag to a column that labels it as the secondary cell that will set where the status is there, right before the more actions button.

    We then add a border underneath that row and the rest of the "columns", render sequentially on new lines. We can add some kind of flag to the cells we want to hide on mobile.

    I'm unsure if there's an attribute we can use for the flag on the Column component – className might be suitable but we'd need to extend the type for it.

    Essentially I'm trying to work towards a solution which builds on the existing table definitions, with minimal intervention for mobile modifications, to try and get a good UX outcome that does not introduce a bunch of brittleness.

    We'd also need to replace the table header with the resource type, but that seems trivial.

    @charliepark @david-crespo

  2. benjaminleonard commented on Mar 11, 2024

    @benjaminleonard
    ContributorAuthor

    Discussed further with Eugene – this approach might break down in places like capacity and utilization wherein the column type cannot be discerned from context alone. Will also work on a horizontally scrollable version for mobile, it's not the ideal user experience but is probably the most flexible.

  3. david-crespo commented on Nov 20, 2026

    @david-crespo
    Collaborator

    @sudomateo said

    the table view still needs some work since long names in the first column don’t leave much space to see the values for subsequent columns. I don't think this should block merge, but I just wanted to provide the feedback since feedback was solicited.

    #3361 (comment)

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

Metadata

Metadata

Labels

designRequires design input

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions